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 skills add felipefontoura/pi-sdd-kit --skill sdd-reviewgit clone --depth 1 https://github.com/felipefontoura/pi-sdd-kitWrote 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/felipefontoura/pi-sdd-kit/sdd-review)<a href="https://agentmods.dev/skills/felipefontoura/pi-sdd-kit/sdd-review"><img src="https://agentmods.dev/badge/skills/felipefontoura/pi-sdd-kit/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/felipefontoura/pi-sdd-kit/sdd-review"><img src="https://agentmods.dev/badge/skills/felipefontoura/pi-sdd-kit/sdd-review.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.00066 | $0.01133 |
| Opus 5 | $0.00033 | $0.00566 |
| Sonnet 5 | $0.00013 | $0.00227 |
| Haiku 4.5 | $0.00007 | $0.00113 |
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 11d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Review
Validate implementation against the approved SDD artifacts.
Purpose
Review checks whether the delivered code matches the product requirements, technical design, task plan, and project quality bar. It creates a concise but actionable review.md artifact.
Workflow
-
Load the SDD reference.
- Read
../_shared/references/sdd-practical.md. - Apply the Language Policy: respond and write artifacts in the user's initial chat language while keeping skill instructions and templates in EN-US.
- Read
../_shared/references/templates.mdwhen writing the review artifact. - Use package-level
templates/review.mdas the user-facing template when available. - Use the SDD Handoff Template and package-level
templates/handoff.mdwhen refreshing.ai/sdd/handoff/sdd-brief.mdafter review. - Load relevant
.ai/steering/*.mdfiles when present, especially conventions, principles, and verification rules.
- Read
-
Locate the feature and validate the gate.
- Use
.ai/sdd/specs/NNN-feature-name/. - Read
.status. - Validate
.statusagainst the official status values fromsdd-practical.md. - If
.statusis missing or invalid, stop and ask the user to repair it; do not infer implementation completion from files or task checkboxes alone. - Prefer reviewing after
implementation:done. - If status is
implementation:in-progress, state that the review is partial and do not set.statustoreview:done. - If status is earlier than
implementation:in-progress, block unless the user explicitly asks for a non-final artifact review. - Read
requirements.md,design.md,tasks.md, anddecisions.mdif present.
- Use
-
Identify review scope.
- Use files listed in
tasks.mdas the starting scope. - Inspect current repository changes when available.
- If scope is unclear, ask the user which files or feature area to review.
- Use files listed in
-
Review against the spec.
- Check each functional requirement and acceptance criterion.
- Check that design decisions and edge cases were implemented or intentionally updated.
- Check task completion claims against actual code.
- Flag missing, partial, or divergent behavior.
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.
- 11d ago First seen · 89 lines · 66 tokens per session scan A ce859886a36e
sdd-review is a skill published in the GitHub repository felipefontoura/pi-sdd-kit (23 stars, last pushed 2mo ago), licensed MIT. It adds 66 tokens to every session and 1,133 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-30.
Other skills, from other repositories
agent-watchdog
Use when asked to watch, babysit, audit, review, compare, or fix another agent's work from a Codex session ID, Claude Code session/transcript, chat/thread link, PR, branch, log, or pasted run summary. Monitor until the other agent is done or blocked, reconstruct what the user asked, independently investigate the same…
comet-verify
Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.
agent-design-best-practices
Best practices for designing Claude Code agent files (.claude/agents/.md). This skill should be used when writing or reviewing agent markdown files to ensure proper design with focused domains, correct tool access, reusable definitions, and separation of capabilities from lifecycle. Combines Anthropic's official…
map-codebase
Deep architecture report that fans out parallel inspections across different aspects of the codebase (structure, tech stack, APIs, patterns, data flow, dependencies, testing) and synthesizes findings into a comprehensive document at .turbo/codebase-map.md and .turbo/codebase-map.html. Use when the user asks to "map…
graphify-dotnet
Use graphify-dotnet to generate codebase knowledge graphs, architecture snapshots, and exportable repository maps from .NET or polyglot source trees, with optional AI-enriched semantic relationships. USE FOR: graphify commands; graph JSON, HTML, SVG, Cypher, Markdown, and Obsidian exports; repository map and…
reply-to-pr-threads
Draft, confirm, and post replies to GitHub PR review threads. Handles per-category reply formatting, re-fetches thread resolution state so auto-resolved threads are skipped, and posts via GraphQL. Use when the user asks to "reply to PR threads", "post PR thread replies", or "draft PR reply messages".