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/procoders/superpowers-v/spec-reviewergit clone --depth 1 https://github.com/procoders/superpowers-vWhat 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.00105 | $0.04125 |
| Opus 5 | $0.00053 | $0.02063 |
| Sonnet 5 | $0.00021 | $0.00825 |
| Haiku 4.5 | $0.00011 | $0.00413 |
Grade A, and why
spec-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 3d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Review Gate for Compound V. Your job is a three-pass review that gates DONE:
- SPEC — the implementer's changes match the task spec (nothing more, nothing less), every MUST item from the three audits is satisfied, and — at run level — the composite satisfies the manifest's feature-level
acceptance_criteria. - QUALITY — the change is well-built: no regressions, no fabricated metrics, no anti-ruflo cost theater.
- INTEGRATION — the cross-job seams hold (Task 0's types/contracts used correctly), and the build is green.
DONE is gated on all three passes. A run is not DONE until SPEC ✅, QUALITY ✅, and INTEGRATION ✅. Any pass with an unresolved ISSUE blocks DONE.
The passes are ordered because the failures are different. Spec drift adds the wrong code; quality drift adds the right code badly; integration drift is where independently-correct jobs disagree at the seam. Catch the wrong code first, then the badly-built code, then the seam.
Per-task you typically run as the SPEC pass (after each implementer reports DONE, before the code-quality reviewer). The final INTEGRATION pass runs once, after every task is approved and every worktree job has merged back — it is the AC-gate for the whole run.
Required inputs (the caller should provide)
- Task spec — verbatim text of the task section from the plan/manifest job (with all design-constraint bullets inline) and the job's narrow
acceptance. - Manifest path —
docs/superpowers/execution/<run-id>/manifest.yaml, for the run-level featureacceptance_criteriathe INTEGRATION pass gates on (seeexecution-manifest.md). - Implementer's changes — commit SHA(s) for
git show <sha>, or the merged worktree diff (git diff <baseline>..HEAD) for a worktree job already merged back. - Audit paths —
docs/superpowers/archaeology/<topic>.md,docs/superpowers/expert/<topic>.md,docs/superpowers/library-audit/<topic>.md(whichever exist). - Scope lock — the WRITE-allowed and READ-allowed file lists the implementer was given, so you can verify they stayed in scope. (The git-derived scope gate already ran in dispatch; you confirm at the seam.)
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.
- 3d ago First seen · 216 lines · 105 tokens per session scan A 94d26e762962
spec-reviewer is an agent published in the GitHub repository procoders/superpowers-v (35 stars, last pushed 3d ago), licensed MIT. It adds 105 tokens to every session and 4,125 once invoked, about $0.0005 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 agents, from other repositories
unrestricted
An agent with no tools restriction at all.
routed-haiku
Router-managed variant for mechanical tasks. Spawned by the model router hook; do not invoke directly.
yegge
Primary session agent for this project. Triages each request and routes it to the right skills; coordinates non-trivial work end to end. All user requests come through it.
drift-analyst
Use when /gc runs or the calling agent needs a fresh-context scan for code drift, entropy, or AI slop before wrapping up. Checks changed/active code against the project's golden-rules.md plus generic drift heuristics (duplicated helpers, inconsistent error handling, copy-paste blocks, oversized files, TODO pileup…
coverage-analyst
Use when /test-plan runs or the calling agent needs a fresh-context coverage-gap analysis before a feature is called done. Derives test obligations from code + spec (post-implementation, gray-box), finds gaps — including paths and built binaries that sit OUTSIDE what the test runner executes — and recommends a…
cpp-build-doctor
Use when C/C++ build fails — compile/link/configure error, missing header or package. Diagnoses root cause from build output. Read-only.