Agent skill

Usenixsec Supplementary

by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills

Install Usenixsec Supplementary

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-supplementary -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-supplementary --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/USENIX-Security-Skills/skills/usenixsec-supplementary .claude/skills/usenixsec-supplementary && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "usenixsec-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-supplementary into .claude/skills/usenixsec-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-supplementary", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-supplementary

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-supplementary -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-supplementary --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/USENIX-Security-Skills/skills/usenixsec-supplementary .agents/skills/usenixsec-supplementary && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "usenixsec-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-supplementary into .agents/skills/usenixsec-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-supplementary", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-supplementary -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-supplementary --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/USENIX-Security-Skills/skills/usenixsec-supplementary .cursor/skills/usenixsec-supplementary && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "usenixsec-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-supplementary into .cursor/skills/usenixsec-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-supplementary", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path USENIX-Security-Skills/skills/usenixsec-supplementary

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-supplementary -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-supplementary --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/USENIX-Security-Skills/skills/usenixsec-supplementary .gemini/skills/usenixsec-supplementary && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "usenixsec-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-supplementary into .gemini/skills/usenixsec-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-supplementary", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-supplementary

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-supplementary -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/USENIX-Security-Skills/skills/usenixsec-supplementary .github/skills/usenixsec-supplementary && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "usenixsec-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-supplementary into .github/skills/usenixsec-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-supplementary", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-supplementary -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-supplementary --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/USENIX-Security-Skills/skills/usenixsec-supplementary .opencode/skills/usenixsec-supplementary && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "usenixsec-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-supplementary into .opencode/skills/usenixsec-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-supplementary", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: usenixsec-supplementary
GitHub stars: 1.2k
Token cost: ~1.3k tokens
SKILL.md length: 588 words
Files: 1
Skills in repo: 2,387
Repo updated: Sep 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Works in 4 steps: Compress prose, not evidence — security… → Merge figures that make one point; move… → Demote per-item tables to an appendix,… → …
Deciding what goes where in a USENIX Security Symposium paper — the 13-page body
SKILL.md covers The four tiers and their…, What must stay inside the 13…, What earns its place in… and Overflow triage when the body…, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Usenixsec Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what goes where in a USENIX Security Symposium paper — the 13-page body, the two mandatory one-page appendices (Ethical Considerations, Open Science), optional appendices after the references, and external artifacts — so nothing decision-critical lands where reviewers won't look.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science, covering Reproducible research. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜覆盖主流期刊的… The licence is MIT.

When your agent uses it

Deciding what goes where in a USENIX Security Symposium paper — the 13-page body
The two mandatory one-page appendices (Ethical Considerations
Optional appendices after the references
External artifacts — so nothing decision-critical lands where reviewers wont look

Example prompts

“/usenixsec-supplementary”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Compress prose, not evidence — security drafts habitually re-narrate tables.
Merge figures that make one point; move third-and-later examples out.
Demote per-item tables to an appendix, keeping the aggregate + the worst case.
Only then consider dropping an experiment — and if it was load-bearing, the

What it can do on your machine

Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are latex).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Usenixsec Supplementary loads about 1.3k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 588 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~81
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 588 words, ~1,322 tokens.

Download SKILL.mdSave it as .claude/skills/usenixsec-supplementary/SKILL.md (or your agent's skills folder).

name: usenixsec-supplementary
description: Use when deciding what goes where in a USENIX Security Symposium paper — the 13-page body, the two mandatory one-page appendices (Ethical Considerations, Open Science), optional appendices after the references, and external artifacts — so nothing decision-critical lands where reviewers won't look.

USENIX Security Supplementary Material

USENIX Security does not collect a separate supplement upload; everything textual travels in one PDF with a fixed geography, and everything executable lives at the locations named in the Open Science appendix. Placement is therefore a reviewing decision: material outside the 13-page body has no guarantee of being read. The layout below is the '26 rule set (checked 2026-07-08); confirm against the current CFP before restructuring a draft.

The four tiers and their reading guarantees

Tier	Cap ('26)	Who reads it
Main body	13 pages	Reviewers, fully — the only tier with a guarantee
Ethical Considerations appendix	~1 page, mandatory	Reviewers and (when flagged) ethics scrutiny — read carefully
Open Science appendix	~1 page, mandatory	Reviewers + AEC after acceptance — enforced, not just read
References + optional appendices	uncapped	Discretionary; assume skimmed at best

The two named appendices sit between the body and the references — an ordering unique enough that template mistakes are common. They are not overflow space: their job is compliance content (see usenixsec-reproducibility and the ethics coverage in usenixsec-topic-selection / usenixsec-experiments), and stuffing evaluation material into them reads as a page-limit dodge.

What must stay inside the 13 pages

Anything a reviewer needs to judge the contribution:

Threat model and assumptions — never appendix material at a security venue.
The core mechanism or attack technique, end to end.
Headline evaluation: main tables/figures, the adaptive-attacker experiment for defenses, the false-positive analysis for detection systems.
Enough dataset description to assess validity (full construction detail can overflow to an optional appendix).
Limitations. Hiding limitations in an appendix is a known reviewer irritant and reads as bad faith at a venue that prizes calibrated claims.

What earns its place in optional appendices

Extended proofs or protocol-analysis detail supporting a body-level statement.
Full per-target or per-CVE result tables where the body shows aggregates.
Additional case studies repeating a body-demonstrated pattern.
Survey instruments, codebooks, disclosure-email templates.
Configuration minutiae an artifact user needs but a reviewer does not.

For each candidate block, apply the demotion test: if a reviewer never reads this, does any claim in the body lose its support? If yes, it stays in the body or the claim gets weakened. If no, demote it and leave a one-line pointer.

Show full SKILL.md (222 more words)Show less

Overflow triage when the body runs long

Cutting to 13 pages is a routing exercise, in priority order:

Compress prose, not evidence — security drafts habitually re-narrate tables.
Merge figures that make one point; move third-and-later examples out.
Demote per-item tables to an appendix, keeping the aggregate + the worst case.
Only then consider dropping an experiment — and if it was load-bearing, the paper may actually be two papers (see usenixsec-topic-selection).

Never solve overflow with template surgery; the CFP forbids whitespace tampering and desk-level format checks are mechanical.

latex

% Correct skeleton ('26 geometry) — verify against the current template
\end{document-body}            % ≤ 13 pages ends here
\section*{Ethical Considerations}   % mandatory, ≤ ~1 page
...
\section*{Open Science}             % mandatory, ≤ ~1 page
...
\bibliographystyle{plain}
\bibliography{refs}                 % uncapped
\appendix
\section{Extended Results}          % optional, uncapped, no reading guarantee
\section{Survey Instrument}

External material: the artifact is the real supplement

Code, data, VM images, and long-form documentation live at the Open Science locations, not in the PDF. Two placement rules connect the tiers:

The PDF should contain everything needed to evaluate the paper; the artifact contains everything needed to redo it. Reviewers are not obliged to open artifact links during review, so no reviewing-critical fact may exist only there.
Anonymization at submission applies to all tiers at once: optional appendices and artifact READMEs leak identity exactly as effectively as page 1 does.

Reverify each cycle

Page caps and the mandatory-appendix allowances in the current CFP ('27 待核实).
Appendix ordering relative to references (this changed style between recent cycles at peer venues; don't assume).
Whether any separate supplemental upload channel has been introduced.

Output format

text

[Geometry] body pages / named appendices present in order / optional appendix count
[Demotion audit] items moved out + demotion-test result for each
[Body integrity] claims fully supported inside 13 pages: yes / gaps
[External] artifact-only material list — nothing reviewing-critical: confirmed

Files

Just SKILL.md in USENIX-Security-Skills/skills/usenixsec-supplementary of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Usenixsec Supplementary next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Usenixsec Supplementary compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Usenixsec Supplementary this skillbrycewang-stanford/Awesome-Journal-Skills	1.2k	—	~1.3k	Automated safety check: Pass	MIT	14 days ago
Peer ReviewK-Dense-AI/claude-scientific-writer	2.4k	2 repos	~3.1k	Automated safety check: Notes	MIT	2 days ago
CHARLS Paper Reproduction Guidexjtulyc/MedgeClaw	617	1 repos	~1.8k	Automated safety check: Pass	None	7 mo ago
Compute Environment Setupaipoch/open-science	5.5k	—	~2.6k	Automated safety check: Pass	Apache-2.0	today
Figure Styleaipoch/open-science	5.5k	—	~5.1k	Automated safety check: Pass	Apache-2.0	today
Add Bactopia Toolbactopia/bactopia	522	—	~4.1k	Automated safety check: Pass	MIT	2 mo ago

Similar skills

Peer Review
K-Dense-AI/claude-scientific-writer
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.
2.4k GitHub starsUsed in 2 repos~3.1k tokens
Research & ScienceAuto-check: notes
CHARLS Paper Reproduction Guide
xjtulyc/MedgeClaw
Guides an agent through reproducing papers built on the CHARLS health and retirement survey, from variable mapping to cognition, depression and isolation scores.
617 GitHub starsUsed in 1 repo~1.8k tokens
Research & ScienceAuto-check passed
Compute Environment Setup
aipoch/open-science
Prepares setup instructions and a named activation file for a user-managed software environment on an Open-Science SSH or Slurm compute host.
5.5k GitHub stars~2.6k tokensUpdated today
Research & ScienceAuto-check passed
Figure Style
aipoch/open-science
Publication-grade correctness and legibility rules for final-deliverable scientific figures, not exploratory plots.
5.5k GitHub stars~5.1k tokensUpdated today
Research & ScienceAuto-check passed
Add Bactopia Tool
bactopia/bactopia
Scaffold a complete Bactopia Tool across all three tiers -- module, subworkflow, and workflow entry point under workflows/bactopia-tools/.
522 GitHub stars~4.1k tokensUpdated 2 mo ago
Research & ScienceAuto-check passed
Modeling Code and Result Contracts
yushui2022/MathModel-Skill
Generates result-evidence contracts, tables and runnable q1 to q3 modeling code scaffolds for a math modeling paper from a model route, a data plan and cleaned data.
454 GitHub stars~1.4k tokensUpdated 4 days ago
Research & ScienceAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo

Aaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
1.2k GitHub stars~1.4k tokensUpdated 14 days ago
Auto-check passed
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
1.2k GitHub stars~1.4k tokensUpdated 14 days ago
Auto-check passed
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
1.2k GitHub stars~1.6k tokensUpdated 14 days ago
Auto-check passed

Questions about Usenixsec Supplementary

What does Usenixsec Supplementary do?

A skill your agent uses when deciding what goes where in a USENIX Security Symposium paper — the 13-page body, the two mandatory one-page appendices (Ethical Considerations, Open Science), optional…. Usenixsec Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what goes where in a USENIX Security Symposium paper — the 13-page body, the two mandatory one-page appendices (Ethical Considerations, Open Science), optional appendices after the references, and external artifacts — so nothing decision-critical lands where reviewers won't look.

When should I use Usenixsec Supplementary?

Usenixsec Supplementary fits situations like: deciding what goes where in a USENIX Security Symposium paper — the 13-page body; the two mandatory one-page appendices (Ethical Considerations; optional appendices after the references; external artifacts — so nothing decision-critical lands where reviewers wont look.

How do I install Usenixsec Supplementary in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-supplementary -a claude-code`. Or copy the skill folder (USENIX-Security-Skills/skills/usenixsec-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/usenixsec-supplementary in your project. Claude Code loads it when a task matches its description.

How do I install Usenixsec Supplementary in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-supplementary -a codex`. Or copy the skill folder (USENIX-Security-Skills/skills/usenixsec-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/usenixsec-supplementary in your project. Codex loads it when a task matches its description.

Can I use Usenixsec Supplementary in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-supplementary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/usenixsec-supplementary, .gemini/skills/usenixsec-supplementary, .github/skills/usenixsec-supplementary and .opencode/skills/usenixsec-supplementary in your project.

What does Usenixsec Supplementary need to run?

SKILL.md names no scripts, command-line tools or credentials: Usenixsec Supplementary is instructions for the agent only.

Does Usenixsec Supplementary access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Usenixsec Supplementary safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Usenixsec Supplementary use?

Usenixsec Supplementary is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Usenixsec Supplementary use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Usenixsec Supplementary?

Skills that share tags, products or a category with Usenixsec Supplementary: Peer Review (K-Dense-AI/claude-scientific-writer, 2.4k stars), CHARLS Paper Reproduction Guide (xjtulyc/MedgeClaw, 617 stars), Compute Environment Setup (aipoch/open-science, 5.5k stars) and Figure Style (aipoch/open-science, 5.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Usenixsec Supplementary?

brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.

Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Usenixsec Supplementary

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

USENIX Security Supplementary Material

The four tiers and their reading guarantees

What must stay inside the 13 pages

What earns its place in optional appendices

Overflow triage when the body runs long

External material: the artifact is the real supplement

Reverify each cycle

Output format

Files

Compare with similar skills

Similar skills

More from brycewang-stanford/Awesome-Journal-Skills

Related

Questions about Usenixsec Supplementary