usenixsec-supplementary
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.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-supplementary --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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`
- 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
What does the usenixsec-supplementary skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-supplementary --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.