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/skills/sdd-review/SKILL.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/skills/yi-john-huang/sdd-mcp/sdd-review)<a href="https://agentmods.dev/skills/yi-john-huang/sdd-mcp/sdd-review"><img src="https://agentmods.dev/badge/skills/yi-john-huang/sdd-mcp/sdd-review/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/skills/yi-john-huang/sdd-mcp/sdd-review"><img src="https://agentmods.dev/badge/skills/yi-john-huang/sdd-mcp/sdd-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.01286 |
| Opus 5 | $0.00023 | $0.00643 |
| Sonnet 5 | $0.00009 | $0.00257 |
| Haiku 4.5 | $0.00005 | $0.00129 |
Grade A, and why
sdd-review 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 12d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Code Review
Perform comprehensive code reviews in the style of Linus Torvalds - direct, thorough, and focused on what matters: correctness, simplicity, and long-term maintainability.
Review Philosophy
"Talk is cheap. Show me the code." — Linus Torvalds
This review focuses on:
- Correctness - Does it actually work? Does it handle edge cases?
- Simplicity - Is it more complex than necessary?
- Maintainability - Will future developers understand this?
- Convention Adherence - Does it follow project patterns?
Workflow
Step 1: Identify Review Scope
Determine what to review:
- Single file:
/sdd-review src/services/UserService.ts - Directory:
/sdd-review src/services/ - Git diff:
/sdd-review HEAD~3..HEAD - PR/MR:
/sdd-review PR-123or/sdd-review MR-45
Step 2: Load Project Context
Before reviewing:
- Read project steering documents from
.spec/steering/ - Understand existing patterns in the codebase
- Check if there's a related spec in
.spec/specs/
Step 3: Perform Review
Code Correctness Checks
## Correctness Issues
### Critical
- [ ] Logic errors that will cause bugs
- [ ] Race conditions or threading issues
- [ ] Resource leaks (files, connections, memory)
- [ ] Unhandled error conditions
### Important
- [ ] Edge cases not handled
- [ ] Assumptions that may not hold
- [ ] Off-by-one errors
- [ ] Type mismatches or unsafe casts
Simplicity Assessment
Ask these questions:
- Could this be done with less code?
- Is there a standard library function for this?
- Is this abstraction earning its keep?
- Would a junior developer understand this in 6 months?
Pattern Violations
Check against project conventions:
## Pattern Violations
### Naming
- [ ] Variables don't follow naming convention
- [ ] Functions named for implementation, not purpose
### Structure
- [ ] Logic in wrong layer (controller doing business logic)
- [ ] Missing separation of concerns
- [ ] Circular dependencies introduced
### Error Handling
- [ ] Swallowed exceptions
- [ ] Generic error messages
- [ ] Missing error propagation
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.
- 12d ago First seen · 192 lines · 47 tokens per session scan A 23eca008a62e
sdd-review is a skill published in the GitHub repository yi-john-huang/sdd-mcp (51 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 1,286 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-30.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…