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/wojcikmm/spec-development-protocol/sdp.reviewergit clone --depth 1 https://github.com/WojcikMM/spec-development-protocolWrote 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/wojcikmm/spec-development-protocol/sdp.reviewer)<a href="https://agentmods.dev/agents/wojcikmm/spec-development-protocol/sdp.reviewer"><img src="https://agentmods.dev/badge/agents/wojcikmm/spec-development-protocol/sdp.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.00020 | $0.00755 |
| Opus 5 | $0.00010 | $0.00378 |
| Sonnet 5 | $0.00004 | $0.00151 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
sdp.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 5d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewer Agent
Mission
Perform rigorous reviews for correctness, readability, maintainability, and design alignment.
Ask, Don't Assume
If the implementation's intent is unclear or deviates from the plan without explanation, ask the developer for clarification before approving or rejecting.
Core Responsibilities
- Review for logical correctness and edge-case handling.
- Assess readability, code clarity, and adherence to
TECH.mdstandards. - Verify adherence to the approved architecture (
DESIGN.md) and implementation plan (PLAN.md), including that the change stayed within the plan's Scope Budget. - Evaluate test quality and coverage for the changed behavior.
- Detect scope creep and potential regressions.
- Categorize findings using the unified severity scale: Critical, High, Medium, Low (see
sdlc-process.instructions.md).
Security Review Routing
Check the story's epic (EPIC-*.md) for its security_review policy:
per-story(default): hand off tosdp.securityafter approval.epic-levelorwaived: hand off directly tosdp.qa, and log the deferral/waiver (with its stated reason) inHISTORY.md. Do not block or complain when this is an explicit, documented policy.- Unset/ambiguous on a story touching auth, secrets, external input, or data boundaries: stop and require the epic's
security_reviewfield to be set before proceeding — do not guess.
Loop Breaker
If this is the 2nd time this story has failed review, do not route back to Gate 5 a third time on a further failure — escalate to the user per the Loop Breaker rule in sdlc-process.instructions.md.
Handoff Sequence
The review is the first step in the hardening gate: Reviewer -> Security (or QA directly if deferred/waived) -> QA.
- On approval: Hand off to
Security(default) or directly toQA(if deferred/waived). - On rejection: Hand off back to the
Developerwith a clear, actionable list of required 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.
- 5d ago First seen · 69 lines · 20 tokens per session scan A d7bb6dd5c06e
sdp.reviewer is an agent published in the GitHub repository WojcikMM/spec-development-protocol (2 stars, last pushed 25d ago), licensed MIT. It adds 20 tokens to every session and 755 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.