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 viamus/claude-sdd-plugin --skill sdd-checkgit clone --depth 1 https://github.com/viamus/claude-sdd-pluginWrote 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/viamus/claude-sdd-plugin/sdd-check)<a href="https://agentmods.dev/skills/viamus/claude-sdd-plugin/sdd-check"><img src="https://agentmods.dev/badge/skills/viamus/claude-sdd-plugin/sdd-check/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/viamus/claude-sdd-plugin/sdd-check"><img src="https://agentmods.dev/badge/skills/viamus/claude-sdd-plugin/sdd-check.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.00039 | $0.00773 |
| Opus 5.5 | $0.00016 | $0.00309 |
| Sonnet 5.5 | $0.00008 | $0.00155 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
sdd-check 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 1mo 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Check — Consistency Verification
You are the SDD Orchestrator verifying that implementation code is consistent with its specification.
Instructions
-
Determine which specs to check:
- If
$ARGUMENTScontains--all: check ALL approved specs withoutput_files - If
$ARGUMENTSis provided (one or more paths): use each one - If no arguments: search
specs/for files withstatus: approvedthat haveoutput_filesdefined- If multiple found, ask: "Found X specs with generated code. Check all, or pick specific ones?"
- If none found, say: "No specs with generated code found."
- For multiple specs, process each one and generate a unified summary at the end
- If
-
Read the spec file completely
-
Read the
output_fileslisted in the spec frontmatter- If
output_filesis empty, try to find related code by matching file names against the spec name
- If
-
Perform consistency checks:
Check Matrix
| # | Check | How to Verify |
|---|---|---|
| 1 | Interface Match | Input types in code match spec's Inputs table |
| 2 | Output Match | Return types in code match spec's Outputs table |
| 3 | Business Rules | Each numbered rule in spec has corresponding logic in code |
| 4 | Error Handling | Each error scenario in spec has a corresponding catch/throw/return |
| 5 | No Extra Features | Code doesn't implement functionality not in the spec |
| 6 | Dependencies Used | Libraries listed in spec are the ones used in code |
- Generate consistency report:
## 🔍 SDD Consistency Report: {spec-name}
**Spec:** specs/{name}.spec.md
**Code:** {list of code files}
### Results
| # | Check | Status | Details |
|---|-------|--------|---------|
| 1 | Interface Match | ✅/❌ | ... |
| 2 | Output Match | ✅/❌ | ... |
| 3 | Business Rules | ✅/❌ | X/Y rules implemented |
| 4 | Error Handling | ✅/❌ | X/Y scenarios covered |
| 5 | No Extra Features | ✅/⚠️ | ... |
| 6 | Dependencies | ✅/❌ | ... |
### Divergences Found
<!-- List specific mismatches -->
### Recommendations
<!-- For each divergence, suggest: fix code OR update spec -->
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.
- 1mo ago First seen · 81 lines · 39 tokens per session scan A 5b4d1e1c9cd9
sdd-check is a skill published in the GitHub repository viamus/claude-sdd-plugin (4 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 773 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
auto-review
Use this skill to configure and understand the built-in auto-review plugin (wstack-auto-review) that fires automated code review subagents on every code change during a session. Triggers: user says "auto review", "otomatik review", "auto code review", "her değişiklikte review", "/auto-review".
codex-adversarial-review
Use this skill to conduct aggressive, adversarial code reviews on git changes, branches, or PRs to detect critical edge cases, race conditions, security holes, and data loss risks. Triggers: user mentions "adversarial review", "break the code", "find vulnerabilities", "security audit PR", "race condition check", "ship…
code-review
Use this skill when asked to review code changes — a pull request, a branch, a commit range, or the current diff — for correctness, security, and maintainability before they merge. Triggers: user says "review", "code review", "review this PR", "review my changes", "look over the diff", "is this ready to merge", "PR…
code-quality
Find and remove unused code, ghost dependencies, unnecessary coupling and bundle waste with source-confirmed reachability. Use when cleaning exports or packages, reviewing Knip output or reducing dead code; use security-scanner for security findings and preserve public/dynamic entrypoints.
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…
skill-distiller
Fetches top-rated skills from skills.sh, analyzes them, and synthesizes one token-efficient skill combining the best elements. Use when the user asks to "distill skills for X", "find and combine skills for X", "synthesize skills", "merge skills", "make a skill for X from skills.sh", "update distilled skill", or…