usenixsec-submission
Use when finalizing a USENIX Security Symposium submission — the per-cycle HotCRP site, the registration deadline a week before the paper deadline, the 13-page body plus mandatory Ethical Considerations and Open Science appendices, double-blind sweeps, and the early-reject exposure of a weak upload.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-submission --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 Submission Final gate before a paper enters a USENIX Security cycle. The numbers below are the '26 and '27 cycle values read from usenix.org pages on 2026-07-08 (direct fetches of usenix.org returned 403 in the verification environment, so pages were read through search-engine renderings and cross-checked against the per-cycle HotCRP deadline pages). Reopen the live CFP before trusting any date or cap. ## Two dates per cycle, and the first one bites Every USENIX Security cycle opens with a **mandatory paper registration** roughly one week ahead of the submission deadline. Registration creates the HotCRP record — title, abstract, authors, topics, conflicts — and a paper that was never registered cannot be uploaded later, no matter how finished the PDF is. | Gate | Sec '26 Cycle 1 | Sec '26 Cycle 2 | Sec '27 Cycle 1 | Sec '27 Cycle 2 | |---|---|---|---|---| | Registration | Aug 19, 2025 | Jan 29, 2026 | Aug 18, 2026 | Jan 19, 2027 | | Paper upload | Aug 26, 2025 | Feb 5, 2026 | Aug 25, 2026 | Jan 26, 2027 | | Clock | 11:59 pm AoE | 11:59 pm AoE | 待核实 (assume AoE) | 待核实 (assume AoE) | Each cycle runs its own HotCRP instance (the '26 sites were `sec26cycle1.usenix.hot
- Two dates per cycle, and the first one bites
- The page geometry is unusual — learn it before the deadline
- Anonymity, in USENIX Security's own terms
- Early reject makes sloppy uploads expensive
- Pre-upload audit order
- Reverify each cycle
- Output format
Run on the exact PDF you intend to upload pdftotext sub.pdf - | grep -nEi 'our (prior|previous) work|as we showed' | head pdftotext sub.pdf - | grep -nEi 'github\.com/|gitlab\.|acknowledg|funded by' | head pdfinfo sub.pdf | grep -Ei 'author|creator|producer' grep -rEl 'institution|\\author' *.tex # stray identity in source before rebuild
What does the usenixsec-submission skill do?
Use when finalizing a USENIX Security Symposium submission — the per-cycle HotCRP site, the registration deadline a week before the paper deadline, the 13-page body plus mandatory Ethical Considerations and Open Science appendices, double-blind sweeps, and the early-reject exposure of a weak upload.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-submission --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.