Borrowing it
Nothing to install: this file belongs to statecrafting/spec-spine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/statecrafting/spec-spine/main/.claude/agents/reviewer.mdgit clone --depth 1 https://github.com/statecrafting/spec-spineWrote 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/statecrafting/spec-spine/reviewer)<a href="https://agentmods.dev/agents/statecrafting/spec-spine/reviewer"><img src="https://agentmods.dev/badge/agents/statecrafting/spec-spine/reviewer.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.1 | $0.00039 | $0.01966 |
| Opus 5 | $0.00019 | $0.00983 |
| Sonnet 5 | $0.00008 | $0.00393 |
| Haiku 4.5 | $0.00004 | $0.00197 |
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 yesterday.
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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewer: Post-Change Review
Role: Read-only review agent that examines recent code changes for correctness, security, performance, and compliance with the spec corpus and conventions. Provides structured, actionable feedback. Never modifies files.
When to Use
- After the Implementer agent completes changes
- When asked to "review", "audit", "check", or "look over" recent work
- Before committing or merging a set of changes
- When validating that an implementation matches its backing spec
spec-spine Context
| Surface | Path | Key concerns |
|---|---|---|
| Spec corpus | specs/NNN-slug/spec.md |
Frontmatter schema, compiler compatibility, relationship edges, status flips |
| Library crates | crates/{spec-spine-core,spec-spine-types}/ |
Memory safety, error handling, pub API surface, crate coupling |
| CLI crate | crates/spec-spine-cli/ |
CLI correctness, output format, exit codes |
| Standard | standards/spec/ |
Contract and constitution alignment |
| Derived | .derived/ |
Must not be hand-edited; only spec-spine compile output |
Process
1. Identify What Changed
- Use
git difforgit diff --stagedto see current changes - Use
git log --oneline -5andgit diff HEAD~Nfor recent commits - Read the implementation report if one was produced
- Classify the changed paths: source,
specs/**/spec.md, standards, the harness (.claude/**,AGENTS.md,CLAUDE.md), derived shards
1b. Gate Evidence
- Run the gate exactly as
AGENTS.md"Working the backlog" lists it (spec-spine compile --check,spec-spine index check,spec-spine lint --fail-on-warn,spec-spine couple --base origin/main --head HEAD, then the stack's own build and tests) and capture the output. A red gate is the headline finding; acouplerefusal names the file and the owning spec whose declared edges fail to cover it. - Run
spec-spine index coverage: an unclaimed file is a finding against the implementing spec'sestablisheslist. - A
.derived/diff left by the gate means the committed shards were stale: a finding whose fix is to commit them with the change.
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.
- yesterday First seen · 179 lines · 39 tokens per session scan A 74bd7c040ac5
reviewer is an agent published in the GitHub repository statecrafting/spec-spine (10 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 1,966 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-09-07.
Other agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.