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-writing-stylegit 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-writing-style)<a href="https://agentmods.dev/skills/brycewang-stanford/awesome-journal-skills/asplos-writing-style"><img src="https://agentmods.dev/badge/skills/brycewang-stanford/awesome-journal-skills/asplos-writing-style/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-writing-style"><img src="https://agentmods.dev/badge/skills/brycewang-stanford/awesome-journal-skills/asplos-writing-style.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.00065 | $0.01449 |
| Opus 5 | $0.00032 | $0.00724 |
| Sonnet 5 | $0.00013 | $0.00290 |
| Haiku 4.5 | $0.00006 | $0.00145 |
Grade A, and why
asplos-writing-style 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 Writing Style
Two 2027 mechanics dictate ASPLOS prose (CFP, checked 2026-07-08): the rapid review reads only the first two pages, and the 11-page limit counts all text, figures, tables, and footnotes — references excluded. The first makes pages 1-2 a survival organ; the second makes every figure a budget decision. Style here is mostly resource allocation.
Engineering pages 1-2 as a standalone document
By the bottom of page 2, a screener must hold four things. Audit for them mechanically, in order:
| Element | Test | Common failure |
|---|---|---|
| Cross-layer problem | Can a reader from any of the three communities restate it? | A single-community problem with "co-design" sprinkled on |
| One-sentence insight | Is there a sentence a screener could quote in their note? | Insight diffused across three paragraphs, or a category ("we co-design X and Y") instead of an idea |
| Mechanism sketch | Does the reader know what each layer does? | Architecture described, software hand-waved (or vice versa) |
| Headline evidence | Result + platform class (silicon/FPGA/simulator) + baseline named? | "Significant improvements on a variety of workloads" |
Corollary: background sections, notation, and roadmaps do not belong on pages 1-2.
The worked example (../../resources/worked-examples/01-introduction.md) shows a
full before → after against exactly this table.
The insight sentence
The load-bearing sentence in an ASPLOS paper names information or capability that crosses a layer boundary: what the hardware knows that the OS needs, what the compiler can prove that the microarchitecture can exploit. Drafting discipline:
Weak: "We propose a hardware/software co-designed approach to memory tiering."
(names a category and a topic; contains no idea)
Strong: "The contention data the OS needs already passes through the memory
controller on every access; the fix is a narrow architectural channel,
not a smarter kernel heuristic."
(names the information, its current location, and the boundary moved)
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 · 65 tokens per session scan A 7ecd9321295b
asplos-writing-style is a skill published in the GitHub repository brycewang-stanford/Awesome-Journal-Skills (1,109 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 1,449 once invoked, about $0.0003 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
ai-slop
Operational rubric that turns "don't make AI slop" into observable properties, severity levels, evidence requirements, and repair actions for interface design. Use as the reference rubric when building or reviewing marketing sites, product interfaces, dashboards, portfolios, or e-commerce pages, especially alongside…
fin-submit-check
A pre-submission checklist for an academic paper and its LaTeX files. It checks journal requirements such as anonymous authorship, length, spacing, margins, citations, figures, data availability, and other submission details.
code-review-subagent
Sous-agent spécialisé dans la revue de code automatisée, déclenchable par un agent parent pour analyser du code, un diff ou une PR. Produit un rapport structuré avec findings classés par sévérité, corrections copiables et score qualité. Se déclenche avec "sous-agent review", "code review agent", "automated code…
tej-variable-mapper
A mapping guide between variable definitions in international research databases and fields in TEJ, a Taiwanese financial and economic data service. It records the original formulas, possible TEJ fields, accounting differences, and uncertainty.
public-disclosure-scout
A research skill for finding companies’ own public disclosures from free official sources, especially in Taiwan. It uses sources such as MOPS, the Taiwan Stock Exchange, government data sites, and patent searches; MOPS is Taiwan’s public-company disclosure system.
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…