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-statusgit 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-status)<a href="https://agentmods.dev/skills/viamus/claude-sdd-plugin/sdd-status"><img src="https://agentmods.dev/badge/skills/viamus/claude-sdd-plugin/sdd-status.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.00027 | $0.00482 |
| Opus 5 | $0.00014 | $0.00241 |
| Sonnet 5 | $0.00005 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
sdd-status 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 8d 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.
What it actually says
SDD Status — Workflow Overview
You are the SDD Orchestrator showing the current state of all specifications.
Instructions
- Search for all
*.spec.mdfiles in thespecs/directory - For each file, read the frontmatter to extract:
name,status,created_at,updated_at,depends_on,unlocks,output_files - Display a summary table:
## 📊 SDD Status — {project name}
| Spec | Status | Depends On | Unlocks | Generated Files |
|------|--------|------------|---------|-----------------|
| ... | 🟠 building / 🟡 draft / 🔵 review / 🟢 approved | ... | ... | ... |
**Summary:** X specs total | Y draft | Z approved
- If there are dependencies, show the dependency graph:
## 🔗 Dependency Chain
user-auth ──▶ payment ──▶ billing
│
└──▶ notification
database ──▶ payment
- If no specs found, display:
No specs found in the project.
To get started:
/sdd:sdd-init <component-name>
-
Also check for memory files in
specs/.memory/to show active build sessions -
Flag dependency issues:
🚫 Dependency issues:
- payment depends on user-auth, but user-auth is still in draft
- billing depends on payment, which has no generated code yet
- If any specs are stale or need attention, flag them:
⚠️ Specs that need attention:
- {name}: Approved but no code generated — run /sdd:sdd-gen
- {name}: In draft for X days — finalize or archive
- {name}: In building — resume with /sdd:sdd-build {name}
Rules
- This is a READ-ONLY operation
- Sort by status: building first, then draft, then review, then approved
- Keep output concise
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.
- 8d ago First seen · 71 lines · 27 tokens per session scan A a2eda58f77dc
sdd-status is a skill published in the GitHub repository viamus/claude-sdd-plugin (4 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 482 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 skills, from other repositories
context
A shared reference for Reqord's data model and command-line rules. Reqord uses records such as requirements, specifications, project context, and feedback to organise requirements-driven development.
feedback
A feedback-management skill from the Reqord project, including commands for handling feedback and checking the repository.
setup
A setup and prerequisite check for the Reqord plugin. It checks required command-line tools, GitHub sign-in, and whether a project has been initialized.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…
brief
A Reqord workflow for preparing a brief from project scope and context. Reqord is a requirements-management tool, and the workflow includes argument handling and a detailed specification mode.
status
A Reqord progress dashboard for requirements and specifications. It groups work by status and lists design-document readiness and unresolved feedback.