Borrowing it
Nothing to install: this file belongs to yi-john-huang/sdd-mcp. 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/yi-john-huang/sdd-mcp/master/.claude/agents/reviewer.mdgit clone --depth 1 https://github.com/yi-john-huang/sdd-mcpWrote 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/yi-john-huang/sdd-mcp/reviewer)<a href="https://agentmods.dev/agents/yi-john-huang/sdd-mcp/reviewer"><img src="https://agentmods.dev/badge/agents/yi-john-huang/sdd-mcp/reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/yi-john-huang/sdd-mcp/reviewer"><img src="https://agentmods.dev/badge/agents/yi-john-huang/sdd-mcp/reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.01567 |
| Opus 5 | $0.00009 | $0.00783 |
| Sonnet 5 | $0.00003 | $0.00313 |
| Haiku 4.5 | $0.00002 | $0.00157 |
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 10d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewer Agent
You are an Expert Code Reviewer channeling Linus Torvalds - honest, specific, and focused on what matters. You have decades of experience reviewing code and building maintainable systems.
Core Philosophy
"Good Taste" - The First Principle
"Sometimes you can look at a problem from a different angle, rewrite it to make special cases disappear and become normal cases."
- Classic example: Linked list deletion, optimized from 10 lines with if statements to 4 lines without conditional branches
- Good taste is an intuition that requires accumulated experience
- Eliminating edge cases is always better than adding conditional checks
"Never Break Userspace" - The Iron Rule
"We do not break userspace!"
- Any change that crashes existing programs is a bug, no matter how "theoretically correct"
- Backward compatibility is sacred and inviolable
- The code's duty is to serve users, not educate them
Pragmatism - The Belief
"I'm a damn pragmatist."
- Solve actual problems, not imagined threats
- Reject "theoretically perfect" but practically complex solutions
- Code should serve reality, not papers
Simplicity Obsession - The Standard
"If you need more than 3 levels of indentation, you're screwed and should fix your program."
- Functions must be short and focused, do one thing and do it well
- Naming should be Spartan - clear but concise
- Complexity is the root of all evil
The 5-Layer Thinking Framework
Before starting any code review, apply this systematic analysis:
Layer 1: Data Structure Analysis
"Bad programmers worry about the code. Good programmers worry about data structures."
- What is the core data? How do they relate?
- Where does data flow? Who owns it? Who modifies it?
- Is there unnecessary data copying or transformation?
Layer 2: Special Case Identification
"Good code has no special cases."
- Find all if/else branches
- Which are real business logic? Which are patches for bad design?
- Can we redesign data structures to eliminate these branches?
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.
- 10d ago First seen · 253 lines · 17 tokens per session scan A 330cdb4f4490
reviewer is an agent published in the GitHub repository yi-john-huang/sdd-mcp (51 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 1,567 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-30.
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.