Awesome Journal Skills is a collection of agent skill packs tailored to hundreds of academic journals across fields including economics, social science, medicine, science, and engineering. Researchers use the packs for tasks such as choosing topics, designing empirical strategies, preparing tables and figures, submitting papers, and responding to reviewers. The catalogue entries are the project's journal-specific skills and related plugins.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-workflowgit clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-SkillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/brycewang-stanford/awesome-journal-skills/asplos-workflow)<a href="https://agentmods.dev/skills/brycewang-stanford/awesome-journal-skills/asplos-workflow"><img src="https://agentmods.dev/badge/skills/brycewang-stanford/awesome-journal-skills/asplos-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/brycewang-stanford/awesome-journal-skills/asplos-workflow"><img src="https://agentmods.dev/badge/skills/brycewang-stanford/awesome-journal-skills/asplos-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00074 | $0.01589 |
| Opus 5 | $0.00037 | $0.00794 |
| Sonnet 5 | $0.00015 | $0.00318 |
| Haiku 4.5 | $0.00007 | $0.00159 |
Grade A, and why
asplos-workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ASPLOS Workflow
An ASPLOS campaign is a pipeline with two entry gates per edition and a revision side-channel, not a single deadline sprint. All dates below are the verified 2027 cycle (CFP and conference site, checked 2026-07-08); reopen the official pages before committing a team to any of them.
The 2027 cycle as a calendar
| Gate | April cycle | September cycle |
|---|---|---|
| Full-paper deadline (11:59 PM AoE) | April 15, 2026 — passed | September 9, 2026 — the live gate |
| Author response | July 6-9, 2026 — open this week (as of 2026-07-08) | December 1-4, 2026 |
| Notification | July 27, 2026 | December 21, 2026 |
| Major Revision due | camera-ready deadline, 6 weeks after notification | camera-ready deadline, 6 weeks after notification |
| Conference | April 11-15, 2027, Heraklion, Crete, Greece | same |
There is no separate abstract deadline in 2027, and no mid-year third round — the edition moved from three deadlines to two. Missing September means waiting for the next edition's first gate.
Working backward from September 9, 2026
A credible countdown for a systems paper with hardware-dependent evidence:
T-10 weeks (by ~Jul 1) Freeze the claim list; run asplos-topic-selection;
choose evidence instruments (silicon / FPGA / simulator).
T-8 weeks Evaluation infrastructure done: baselines building,
workloads chosen, simulator configs pinned.
T-6 weeks First full results sweep; kill or descope claims the
data will not carry. Start the two-page draft NOW —
it is the part rapid review actually reads.
T-4 weeks Full draft; internal red-team against the rapid-review
question set; ablations running.
T-2 weeks Freeze experiments. Citation-format pass (full names,
no "et al.", DOIs). Anonymity sweep.
T-1 week HotCRP entry created; PDF uploaded; co-author sign-off.
T-0 Sep 9, 11:59 PM AoE HotCRP status shows *complete*, not draft.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today First seen · 127 lines · 74 tokens per session scan A 74b2a106cdc2
asplos-workflow is a skill published in the GitHub repository brycewang-stanford/Awesome-Journal-Skills (1,109 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 1,589 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-15.
Other skills, from other repositories
council
Five independent critic subagents in parallel on an idea, plan, design, R&R strategy, grant, or SKILL.md, then a synthesis pass that ranks findings by how much of the argument rests on them, never by vote count. A markdown work plan gets the plan roster (assumptions, pre-mortem, what to delete, alternatives per piece…
continual-learning
Nightly refinement of an existing per-repo review-style prompt using this reviewer's own finding outcomes. Read confirmed (resolved-by-commit / thumbs-up) and dismissed (thumbs-down) findings, promote the bug patterns the team actually fixes, demote the false-positive patterns, reconcile against the current prompt…
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
security-review
Perform a focused security review of pending git changes to identify high-confidence security vulnerabilities with real exploitation potential. Use this skill when the user asks for a security review, security audit, vulnerability scan, or wants to check pending changes on a branch for security issues before merging.…
one-way-door
Flags irreversible decisions before commit. Use for data models, infra, auth boundaries, API contracts, event schemas, CI/CD.
make-pr-easy-to-review
Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".