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 aejmic-rebuttalgit 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/aejmic-rebuttal)<a href="https://agentmods.dev/skills/brycewang-stanford/awesome-journal-skills/aejmic-rebuttal"><img src="https://agentmods.dev/badge/skills/brycewang-stanford/awesome-journal-skills/aejmic-rebuttal/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/aejmic-rebuttal"><img src="https://agentmods.dev/badge/skills/brycewang-stanford/awesome-journal-skills/aejmic-rebuttal.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.00000 | $0.01204 |
| Opus 5.5 | $0.00000 | $0.00482 |
| Sonnet 5.5 | $0.00000 | $0.00241 |
| Haiku 4.5 | $0.00000 | $0.00120 |
Grade A, and why
aejmic-rebuttal 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
R&R Rebuttal & Response Letter (aejmic-rebuttal)
When to trigger
- An AEJ: Micro decision letter arrived with an R&R (minor or major)
- You have referee reports and need a response-letter strategy
- A referee disputes a proof, the generality, or the framing and you must decide concede vs. defend
- You are sequencing the revision so the most important changes land first
How to respond to theory referees
AEJ: Micro referees are subject-matter experts who verify proofs and judge generality and exposition. The response letter must be precise, respectful, and point-by-point. Three recurring axes:
- Correctness: a disputed proof step. Either fix it (and show the corrected argument in the letter), or demonstrate the step is valid with the missing detail. Never wave it away.
- Generality / robustness: "does it extend to X?" Decide whether to (a) prove the extension, (b) add it to
aejmic-robustnessas a result, or (c) explain precisely why the boundary is where it is and add a remark. State the cost of each. - Exposition / scope: "the mechanism is buried" or "the claim is too broad." Re-frame via
aejmic-writing-styleand bound the claim explicitly.
Letter structure
- A short cover note to the editor summarizing the main changes and how the central concern was met.
- Point-by-point replies: quote the comment, state the change, point to the page/line and the new/updated proposition or proof.
- Concede gracefully where the referee is right; defend with argument (not assertion) where you disagree, and offer a compromise (a remark, a restricted claim) when full concession is wrong.
- Keep a changelog of every result that moved (new propositions, relabeled lemmas, added extensions).
Triage the reports before drafting
Not all comments carry equal weight. Sort them:
- Central (editor-flagged): the concern the editor named as decisive — resolve it first and lead the cover note with it.
- Correctness blockers: any disputed proof or claim — must be fully closed, never deferred.
- Generality requests: decide per comment whether to prove, add a robustness result, or bound with a precise argument.
- Exposition / framing: usually cheap to grant; granting them buys goodwill for the points you defend.
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 · 75 lines · 0 tokens per session scan A 17f3609d3269
aejmic-rebuttal is a skill published in the GitHub repository brycewang-stanford/Awesome-Journal-Skills (1,289 stars, last pushed 26d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,204 tokens. 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
research-manager
Use this when starting a new research project or managing a complex, multi-step research workflow.
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…
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…
alterlab-timesfm
Forecasts time series zero-shot with Google's TimesFM foundation models — TimesFM 2.5 (200M, Apache-2.0 weights; ForecastConfig API, XReg covariates) and TimesFM 3.0 (330M, multivariate with native past/future covariates; non-commercial weights) — producing point forecasts and quantile prediction intervals from…
alterlab-anndata
Build, slice, concatenate, read, and write AnnData annotated data matrices (obs, var, X, layers, obsm, uns) — the scverse data STRUCTURE, not an analysis pipeline. Use when creating or wrangling .h5ad/zarr files, managing cell and gene annotations, concatenating batches, or handling layers/obsm/backed-mode; for the…