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 agentmods add instructions/ingar30/reviewer/agents-mdgit clone --depth 1 https://github.com/Ingar30/reviewerWrote 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/instructions/ingar30/reviewer/agents-md)<a href="https://agentmods.dev/instructions/ingar30/reviewer/agents-md"><img src="https://agentmods.dev/badge/instructions/ingar30/reviewer/agents-md.svg" alt="Measured on agentmods" 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 | $0.00852 | $0.00852 |
| Opus 5 | $0.00426 | $0.00426 |
| Sonnet 5 | $0.00170 | $0.00170 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
reviewer AGENTS.md 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 4d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project purpose
This repository builds and runs a reproducible multi-agent reviewer for academic economics papers.
The normal workflow is:
- Put source PDFs in
inputs/. - Preprocess each paper into structured artifacts under
work/<paper_id>/parsed/. - Render run-specific prompts under
work/<paper_id>/prompts/. - Run parser-quality preflight before substantive review.
- Optionally run experimental parser repair planning or overlay repair when parser-quality preflight reports high- or medium-severity parser artifacts.
- Use dynamic reviewer selection by default to choose optional reviewers while mandatory reviewers always run.
- Store the selector decision under
work/<paper_id>/selection/and use the selected reviewer roster for downstream stages. - Rerender prompts for the selected reviewer roster, including parser repair notes when present.
- Run the selected reviewer agents on the parsed artifacts.
- Store and validate reviewer JSON outputs under
work/<paper_id>/reviews/. - Normalize and deduplicate reviewer outputs into an editor bundle.
- Build editor input from the normalized bundle and original reviewer JSON files.
- Run the editor to write the final markdown report under
outputs/<paper_id>/report.md. - Smoke-check the final report.
Canonical file locations
- Source PDFs:
inputs/ - Parsed artifacts:
work/<paper_id>/parsed/ - Parser repair overlays:
work/<paper_id>/repair/ - Reviewer outputs:
work/<paper_id>/reviews/ - Reviewer selection:
work/<paper_id>/selection/ - Final reports:
outputs/<paper_id>/
Path conventions
- If the user refers to a bare source PDF filename, first resolve it under
inputs/. - Prefer project-relative paths over absolute paths when possible.
- Do not assume a file is outside the repo unless the user explicitly says so.
Workflow rules
- Never run reviewer agents directly on a raw PDF if parsed artifacts do not exist.
- Preprocessing comes before review.
- Reviewer agents are configured through
config/reviewers.json. - Dynamic reviewer selection is the default for fresh wrapper runs; static mode is available when all enabled reviewers should run.
- Parser repair is opt-in. When enabled with
--parser-repair planor--parser-repair overlay, run it only after parser-quality preflight and only when high- or medium-severityparser_artifactfindings are reported. - Parser repair overlays route reviewers to safer existing artifacts. In
overlaymode, they may also create narrow LLM-generated repaired artifacts underwork/<paper_id>/repair/repaired_artifacts/, but they must not overwritework/<paper_id>/parsed/or replace OCR, table reconstruction, figure crop regeneration, or deterministic preprocessing fixes. - Internal reviewer agents return structured JSON only.
- Only the editor writes the final markdown report.
- If preprocessing artifacts are missing or clearly poor, fail clearly instead of guessing.
- Editor-only refresh is allowed when parsed artifacts, reviewer JSON, selected reviewer config, and the normalized editor bundle already exist. Rerender prompts, rebuild editor input, rerun only the editor, and then smoke-check the final report.
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.
- 4d ago First seen · 65 lines · 852 tokens per session scan A 46a9b6700a4a
reviewer AGENTS.md is an instructions file published in the GitHub repository Ingar30/reviewer (94 stars, last pushed 1mo ago), licensed MIT. It adds 852 tokens to every session, about $0.0043 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-08-30.
Other instructions, from other repositories
paper2pr AGENTS.md
Instructions for alohays/paper2pr, covering agents.md -- paper2pr: presentation framework, core principles, language policy, speaker notes policy and project scope.
deeptutor AGENTS.md
Instructions for jiadizhunine/deeptutor, covering deeptutor — academic advisor investigation system, what this repo is, when to trigger, language & region and model capability — choose full or lite.
statcite CLAUDE.md
Claude Code instructions for asokore/statcite, covering claude.md: statcite project guide, commands (run in server/), architecture (server/src) and invariants: do not break.
the-adversary CLAUDE.md
Instructions for tasumermaf/the-adversary, covering the adversary — repo identity for claude code, your role as the hub, the rules in force, the engine (never reorder) and where things live.
statcite GEMINI.md
Gemini CLI instructions for asokore/statcite, covering statcite: verify economic statistics before you state them, the rule, writing with economic numbers, fact-checking a draft and when sources disagree.
economics-paper-reviewer CLAUDE.md
Instructions for viplee110/economics-paper-reviewer: This repository is a portable English-only economics paper pre-review skill.