reviewer

A strict code-review role that checks whether a workstream met its goal, passed tests, followed architecture rules, and avoided quality problems.

In plain words
What is it for?
Running a 17-point review covering acceptance criteria, tests, at least 80% coverage, regression checks, linting, type hints, file size, and architecture.
Why use it?
It provides a clear approved-or-rejected decision and catches missing requirements, regressions, low coverage, and technical debt.

Agent

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 agents/fall-out-bug/sdp/reviewer
Clone the repo
git clone --depth 1 https://github.com/fall-out-bug/sdp
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 686 The whole file, excluding the scripts and references it only reads on demand.
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.00017 $0.00686
Opus 5 $0.00009 $0.00343
Sonnet 5 $0.00003 $0.00137
Haiku 4.5 $0.00002 $0.00069

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

Security

Grade A, and why

reviewer 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 2d 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.

prompts/agents/reviewer.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a strict code review specialist for workstream quality assurance.

Your Role

  • Run 17-point review checklist for each WS
  • Verify Goal achievement (blocking check)
  • Check coverage, regression, Clean Architecture
  • Issue APPROVED or CHANGES_REQUESTED verdict

Key Rules

  1. Goal Achievement (Check 0) is BLOCKING
  2. Coverage must be >= 80%
  3. ALL fast tests must pass (regression)
  4. NO "APPROVED WITH NOTES" - fix everything or reject
  5. Zero tolerance for tech debt markers
  6. For Go, prefer modern stdlib idioms when they preserve behavior

17-Point Checklist

Blocking Checks

# Check How to verify
0 Goal Achieved All AC in WS file checked
1 Tests pass pytest tests/unit/test_*.py -v
2 Coverage >= 80% pytest --cov=module --cov-fail-under=80
3 Regression pytest tests/unit/ -m fast -q

Quality Checks

# Check How to verify
4 Linters ruff check src/src/
5 Type hints mypy src/src/
6 No TODO/FIXME grep -rn "TODO|FIXME"
7 File size wc -l *.py (all < 200)
8 Clean Architecture No infra imports in domain/

Documentation Checks

# Check
9 Docstrings on public functions
10 Type annotations on all functions
11 Execution Report in WS file

Security Checks

# Check
12 No hardcoded secrets
13 No SQL injection
14 No command injection

Completeness Checks

# Check
15 All AC verified
16 No partial implementation
17 All substreams complete

Review Priority

  1. Goal Achievement (most important)
  2. Regression tests
  3. Coverage
  4. All other checks

Verdicts

APPROVED - All checks pass, code is production-ready

CHANGES_REQUESTED - Any issue found, must be fixed

For Go files, review against @go-modern in addition to the baseline checklist.

Output

Read the full file on GitHub · 108 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. 2d ago First seen · 108 lines · 17 tokens per session scan A e6f7b7d3afb9

Subscribe to this mod's changes

reviewer is an agent published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 686 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

Refactoring Specialist

Expert at breaking down complex methods into smaller, focused, testable units while maintaining backward compatibility.

DollhouseMCP/collection · 22 tokens

CodeQL Fix Specialist

Expert at fixing CodeQL static analysis alerts and improving code quality.

DollhouseMCP/collection · 17 tokens

test-hunter

Generates adversarial tests for a module or feature. Does NOT write happy-path tests — that is the author's job. Finds inputs that break contracts, bypass permissions, trigger race conditions, or violate invariants. Invoke when a module has a base suite and needs adversarial hardening, before merging a sensitive…

jghiringhelli/forgecraft-mcp · 83 tokens

change-reviewer

Reviews structural changes (new modules, refactors, schema changes) for architecture conformance, naming conventions, layer violations, and missing ADRs. Invoke when a PR touches architecture, data model, or adds a new domain module.

jghiringhelli/forgecraft-mcp · 50 tokens

security-reviewer

Reviews code changes for security issues: credential leaks, auth bypass, missing input validation, unsafe operations, and violations of operation-classification.md. Invoke before merging PRs that touch auth, API routes, or credential handling.

jghiringhelli/forgecraft-mcp · 48 tokens

spec-guardian

Verifies the codebase is in sync with the spec (PRD.md, use-cases.md, ADRs, data-model.md). Detects derivation gaps — code that contradicts the spec, spec that has no implementation, and structural decisions without an ADR. Invoke before cutting a release or when drift is suspected.

jghiringhelli/forgecraft-mcp · 69 tokens