Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add shrekshrek/project-workflow/plugin install project-workflowWrote 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/shrekshrek/project-workflow/spec-quality-reviewer)<a href="https://agentmods.dev/agents/shrekshrek/project-workflow/spec-quality-reviewer"><img src="https://agentmods.dev/badge/agents/shrekshrek/project-workflow/spec-quality-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.00069 | $0.00200 |
| Opus 5 | $0.00034 | $0.00100 |
| Sonnet 5 | $0.00014 | $0.00040 |
| Haiku 4.5 | $0.00007 | $0.00020 |
Grade A, and why
spec-quality-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 6d 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
Response language: Match the calling skill's language. Spec citations preserve source language.
You are the Claude Code adapter for the canonical spec-quality-reviewer.
Before reviewing, read:
${CLAUDE_PLUGIN_ROOT}/docs/reviewers/spec-quality-reviewer.md(read completely; canonical contract)docs/spec-driven.mdif checklist wording is unclear- the target feature's
spec.md,plan.md, andtasks.md
Follow the canonical reviewer spec exactly. Suggest rewrites, but do not edit files.
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.
- 6d ago First seen · 18 lines · 69 tokens per session scan A 9fde9f76c0ed
spec-quality-reviewer is an agent published in the GitHub repository shrekshrek/project-workflow (2 stars, last pushed 2d ago), licensed MIT. It adds 69 tokens to every session and 200 once invoked, about $0.0003 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
arbiter
Strong-tier, different-family, adversarial, ACTING judge with FINAL veto on holistic acceptance. Unlike the lightweight phase-validator (which reads a HANDOFF and checks exit-condition prose), the arbiter re-runs the objective gates itself (typecheck, tests, lint, the phase's command conditions) and judges holistic…
phase-validator
Lightweight handoff validator. Reads a phase or wave agent's HANDOFF and compares it against the stated exit conditions. Returns a structured verdict (pass/fail) with specific reasons. Never modifies files — read-only judge. Spawned by Archon after each phase and by Fleet after each wave agent.
arch-reviewer
Read-only architecture reviewer. Checks files for boundary violations, import rule breaks, and pattern compliance. Does not modify files.
reviewer
Read-only spec-compliance reviewer. Given a parent-assembled spec slice (the phase's plan section + task titles/notes + the named Architecture sections) and the just-built diff, returns a structured pass/fail verdict on whether the implementation matches the spec. Never writes. Invoked by /specmanager-build after the…
red-team
Adversarial diff reviewer. Hunts correctness bugs AND flags cleanup (reuse, simplification, efficiency, altitude) in the changed code, then verifies each finding before reporting. Runs in an isolated context to eliminate author-evaluator bias. Use after implementation, before commit, or standalone to review any diff.…
review-impl
Conformance gate. Verifies the implementation matches the plan, every acceptance criterion is met with quoted test evidence, tests are meaningful, and the suite still passes. Does not hunt correctness bugs, robustness gaps, standards violations, or cleanup, red-team owns those. Use after implementation chunks are…