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 atc-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/atc-writing-style)<a href="https://agentmods.dev/skills/brycewang-stanford/awesome-journal-skills/atc-writing-style"><img src="https://agentmods.dev/badge/skills/brycewang-stanford/awesome-journal-skills/atc-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/atc-writing-style"><img src="https://agentmods.dev/badge/skills/brycewang-stanford/awesome-journal-skills/atc-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.00072 | $0.01163 |
| Opus 5.5 | $0.00029 | $0.00465 |
| Sonnet 5.5 | $0.00014 | $0.00233 |
| Haiku 4.5 | $0.00007 | $0.00116 |
Grade A, and why
atc-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 1mo ago.
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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ATC Writing Style
Write for two audiences in two rounds. In round one, two reviewers read only your two-page extended abstract; in round two, 3-4 reviewers read the full paper. The abstract is review-only, not published, and must stand alone. So ATC writing has a demand no single-round venue makes: the paper's core argument must fit, self-contained, into two pages and expand faithfully into twelve.
The self-standing extended abstract (round-one surface)
A round-one reviewer who reads only the abstract should finish knowing:
- The systems problem — a pain a builder or operator recognizes, in the first breath.
- Why the current design is inadequate — the specific limitation your work removes.
- The contribution — the system or technique, stated as what it does, not "novel."
- The evidence — the real testbed and the headline result (with the metric that matters, e.g., tail latency, throughput at matched cost).
- The honest cost — what the design trades away, named not hidden.
Test it: hand the two pages to a systems colleague without the paper and ask them to state the problem, contribution, testbed, and result. If they cannot, the abstract will lose round one no matter how strong the paper is. A trimmed introduction can work only if it already reads self-contained.
The full-paper arc
ATC papers are implementation-and-measurement narratives:
- Introduction: problem → inadequacy → contribution as systems claims → real-testbed evidence → what changes in practice. Lead with the systems contribution, not a trend sentence.
- Design: the mechanism and the reasons for each choice, tied to the deployment constraint. Reviewers reward a design justified by the problem over one justified by novelty.
- Implementation: enough that a reader believes it was built and could be rebuilt — scale (lines, components), integration points, and what was hard.
- Evaluation: questions first, then answers. End-to-end results and microbenchmarks that isolate the mechanism; baselines that are fair; tails and variance, not just means.
- Costs and limitations: report the trade beside the gain, ideally in the same figure/table. ATC reviewers trust evaluations that volunteer their costs.
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.
- 1mo ago First seen · 90 lines · 72 tokens per session scan A 7f2fbe3f23d5
atc-writing-style is a skill published in the GitHub repository brycewang-stanford/Awesome-Journal-Skills (1,264 stars, last pushed 19d ago), licensed MIT. It adds 72 tokens to every session and 1,163 once invoked, about $0.0003 per session on Opus 5.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
alterlab-qiime2-amplicon
Runs 16S/ITS amplicon (microbiome) analysis with the QIIME 2 distribution (2026.7; the "amplicon" distribution was renamed "qiime2" in 2026.4) in the correct order: manifest import, cutadapt trim-paired primer removal BEFORE dada2 denoise-paired (trunc-len chosen from the demux quality .qzv), feature-classifier…
research-manager
Use this when starting a new research project or managing a complex, multi-step research workflow.
alterlab-phylogenetics
Build phylogenetic trees end-to-end from raw sequences — MAFFT multiple sequence alignment, optional TrimAl trimming, IQ-TREE 3 maximum-likelihood inference with model selection and bootstraps, FastTree for large datasets, then visualize with ETE3 or FigTree. Use when reconstructing trees from sequences (FASTA) for…
alterlab-pydicom
Reads, writes, and manipulates DICOM (Digital Imaging and Communications in Medicine) medical imaging files with the pydicom Python library. Use when reading/writing/modifying DICOM data, extracting pixel data from CT, MRI, X-ray, or ultrasound images, anonymizing DICOM files, working with DICOM metadata and tags…
alterlab-pyhealth
Develops, tests, and validates clinical machine learning models with the PyHealth 2.x healthcare AI toolkit. Use when working with electronic health records (EHR), clinical prediction tasks (mortality, readmission, length of stay, drug recommendation), medical coding systems (ICD, NDC, ATC, CCS), physiological signals…
alterlab-citation-verifier
Verifies that every bibliography entry actually exists by cross-checking Crossref, OpenAlex, Semantic Scholar, and arXiv (no API key required) plus doi.org DOI registration, fuzzy-matching title and authors (difflib ratio >= 0.70), flagging retractions recorded by Crossref (including Retraction Watch data) or…