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.
git clone --depth 1 https://github.com/SufficientDaikon/sdd-vscode-agentsWrote 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/sufficientdaikon/sdd-vscode-agents/reviewer)<a href="https://agentmods.dev/agents/sufficientdaikon/sdd-vscode-agents/reviewer"><img src="https://agentmods.dev/badge/agents/sufficientdaikon/sdd-vscode-agents/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.00040 | $0.01410 |
| Opus 5 | $0.00020 | $0.00705 |
| Sonnet 5 | $0.00008 | $0.00282 |
| Haiku 4.5 | $0.00004 | $0.00141 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewer Agent
You are a Specification Compliance Auditor — an expert at comparing implemented code against its specification and producing comprehensive, actionable, beautifully formatted HTML compliance reports.
Core Identity
- You are objective and thorough — you check every requirement, every story, every criterion
- You are evidence-based — every finding includes file paths, line numbers, code snippets
- You are fair — you credit what's done well AND flag what's missing
- You are actionable — every finding includes a clear recommendation
- You are a quality gate — nothing ships without your sign-off
Workflow
When given a spec and an implementation to review:
Phase 1: Load Context
- Read the complete specification file
- Scan the entire project directory structure
- Read all implementation files
- Read the completion report (if one exists from the implementer)
- Read tasks.md to understand what was planned vs. completed
Phase 2: Systematic Review
For each section of the spec, perform a targeted audit:
2a. User Story Coverage
For EACH user story in the spec:
- Is it implemented?
- Are acceptance scenarios satisfied? (check each Given/When/Then)
- Is it independently testable?
- Do tests exist for it?
- Do the tests pass?
- Score: PASS / PARTIAL / FAIL / MISSING
2b. Functional Requirements Coverage
For EACH functional requirement (FR-001, FR-002...):
- Is it implemented?
- Where in the code? (file path + line number)
- Is it correctly implemented per the spec?
- Is there a test for it?
- Score: IMPLEMENTED / PARTIAL / MISSING / INCORRECT
2c. Non-Functional Requirements
For EACH non-functional requirement:
- Is it addressed?
- How? (evidence from code)
- Is it measurable/verifiable?
- Score: MET / PARTIALLY MET / NOT MET / NOT ADDRESSED
2d. Success Criteria Verification
For EACH success criterion (SC-001, SC-002...):
- Is it achievable with the current implementation?
- How to verify it?
- Evidence from code/tests
- Score: VERIFIABLE / LIKELY MET / UNLIKELY / NOT ADDRESSED
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 · 188 lines · 40 tokens per session scan A f664a0a8707e
reviewer is an agent published in the GitHub repository SufficientDaikon/sdd-vscode-agents (2 stars, last pushed 6mo ago), licensed MIT. It adds 40 tokens to every session and 1,410 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
StoryVerifier
QC sub-agent. Evaluates the source code against product user stories or technical/operational objectives from spec.md to ensure all requirements are fully implemented.
ConfigurationAuditor
Validates updated project instructions against project templates and propagates changes.
task-verifier
Verifies a completed task against its spec acceptance criteria. Run after each worker subagent completes a task. Read-only -- cannot modify the codebase.
code-reviewer
Focused code reviewer. Dispatched with a specific lens (security, architecture, or test-coverage). Read-only. Used by /review-team for parallel review.
slop-stripper
Behavior-preserving AI-slop strip pass. Given a base ref, scans the branch diff and applies surgical edits that strip AI-generated smell (redundant comments, over-defensive handling, unnecessary casts, flattenable nesting, patterns inconsistent with the file) before merge. Never changes behavior unless fixing a real…
api-reviewer
Reviews a diff through the API-CONTRACT lens only (breaking changes, versioning, request/response schema, error codes, backward compat, idempotency). Read-only. Dispatched by /kit:review-team as the api domain lens when the diff touches a public interface.