reviewer AGENTS.md

reviewer AGENTS.md is an instructions file for Codex, OpenCode from Ingar30/reviewer. It costs 852 tokens per session, scanned A, original, MIT.

Instructions for a reproducible system that uses several software agents to review academic economics papers. It processes research PDFs, assigns reviewers, validates their structured results, and combines them for editing.

In plain words
What is it for?
Use it to preprocess papers, check parser quality, choose reviewers, run reviews, validate JSON results, remove duplicate findings, and prepare material for an editor.
Why use it?
It defines where each paper artifact belongs and which checks happen before review, reducing confusion and inconsistent results across review runs. It also records reviewer selection and output validation for later inspection.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/ingar30/reviewer/agents-md
Clone the repo
git clone --depth 1 https://github.com/Ingar30/reviewer

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for reviewer AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/ingar30/reviewer/agents-md.svg)](https://agentmods.dev/instructions/ingar30/reviewer/agents-md)
Your own site
<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>
Per session 852 This file is loaded in full into every session.
When invoked 852 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 4d ago against content hash 46a9b6700a4a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

AGENTS.md · 65 lines

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:

  1. Put source PDFs in inputs/.
  2. Preprocess each paper into structured artifacts under work/<paper_id>/parsed/.
  3. Render run-specific prompts under work/<paper_id>/prompts/.
  4. Run parser-quality preflight before substantive review.
  5. Optionally run experimental parser repair planning or overlay repair when parser-quality preflight reports high- or medium-severity parser artifacts.
  6. Use dynamic reviewer selection by default to choose optional reviewers while mandatory reviewers always run.
  7. Store the selector decision under work/<paper_id>/selection/ and use the selected reviewer roster for downstream stages.
  8. Rerender prompts for the selected reviewer roster, including parser repair notes when present.
  9. Run the selected reviewer agents on the parsed artifacts.
  10. Store and validate reviewer JSON outputs under work/<paper_id>/reviews/.
  11. Normalize and deduplicate reviewer outputs into an editor bundle.
  12. Build editor input from the normalized bundle and original reviewer JSON files.
  13. Run the editor to write the final markdown report under outputs/<paper_id>/report.md.
  14. 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 plan or --parser-repair overlay, run it only after parser-quality preflight and only when high- or medium-severity parser_artifact findings are reported.
  • Parser repair overlays route reviewers to safer existing artifacts. In overlay mode, they may also create narrow LLM-generated repaired artifacts under work/<paper_id>/repair/repaired_artifacts/, but they must not overwrite work/<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.

Read the full file on GitHub · 65 lines

Changes

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.

  1. 4d ago First seen · 65 lines · 852 tokens per session scan A 46a9b6700a4a

Subscribe to this mod's changes

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.