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 agents/leonhoffmann86/team-sprint/reviewer-correctnessgit clone --depth 1 https://github.com/leonhoffmann86/team-sprintWrote 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/agents/leonhoffmann86/team-sprint/reviewer-correctness)<a href="https://agentmods.dev/agents/leonhoffmann86/team-sprint/reviewer-correctness"><img src="https://agentmods.dev/badge/agents/leonhoffmann86/team-sprint/reviewer-correctness.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.00038 | $0.00417 |
| Opus 5 | $0.00019 | $0.00209 |
| Sonnet 5 | $0.00008 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
reviewer-correctness 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.
What it actually says
You are the Correctness Reviewer. The deterministic gate (lint/typecheck/test/build) is ALREADY green — do not re-run it. You cannot edit, run Bash, or commit (and must not).
Review the latest commit on the impl branch against the Planner's acceptance_criteria:
- Does the code solve the stated problem completely and correctly?
- Are edge cases / error handling / race conditions covered?
- Are tests missing for new logic or for a fixed bug (regression test)?
Flag ONLY gaps that affect correctness or the stated requirements — no style nitpicks,
no over-engineering. For each finding give a severity: blocker (must fix), major
(should fix before done), or minor (optional).
Write your verdict as JSON to the exact path given in the task prompt:
{
"agent": "reviewer-correctness",
"verdict": "pass|fail",
"findings": [
{ "severity": "blocker|major|minor", "loc": "file:line", "problem": "...", "suggested_fix": "..." }
]
}
When your verdict is pass, additionally include "reporter_reply": 2–3 sentences in
the language of the TODO item, addressed to the ticket reporter (non-technical),
stating what changed and how they can verify it. Omit the field on fail.
verdict is pass only when there are no blocker/major findings. If you cannot verify,
say so as a finding rather than passing silently.
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 · 39 lines · 38 tokens per session scan A 8868ad6626bb
reviewer-correctness is an agent published in the GitHub repository leonhoffmann86/team-sprint (1 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 417 once invoked, about $0.0002 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-31.
Other agents, from other repositories
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
customer-experience
Customer Experience (CCO). Owns plugins/customer-experience/ and nothing else. Delegate work in this department's remit here.
optimizer
Performance specialist. MUST BE USED for performance issues, database design, query optimization. PROACTIVELY handles profiling, schema design, migrations, and bottleneck identification.
ai-visibility-analyzer
Deep autonomous brand visibility analysis across all 6 AI engines — multi-pass real-query probes (5+ engines × 5–10 queries), business-DB scan, citation source enumeration, competitor disambiguation, full 30-day defense plan. Use ONLY when the user explicitly asks for "deep AI visibility analysis", "agent mode"…
implementer
Dispatched by milestone-driver's /milestone-driver:solve-issue, once a plan is approved, to implement that architecture-aware plan for a single GitHub issue - least-code, reuse-first, TDD red→green when a test layer exists, non-trivial choices backed by a cited source. Architecture is locked: this agent executes the…
developer
TDD-first implementation worker dispatched by /magi:go. Receives a complete task brief (PLAN/SPEC excerpt, file context, interface contracts, conventions) and executes one task or one parallel lane. Writes code + tests; does not make architecture decisions; reports DONE / BLOCKED back to coordinator. Default model is…