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 agentmods add instructions/joestump/claude-plugin-sdd/claude-mdgit clone --depth 1 https://github.com/joestump/claude-plugin-sddWrote 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/instructions/joestump/claude-plugin-sdd/claude-md)<a href="https://agentmods.dev/instructions/joestump/claude-plugin-sdd/claude-md"><img src="https://agentmods.dev/badge/instructions/joestump/claude-plugin-sdd/claude-md.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.01446 | $0.01446 |
| Opus 5 | $0.00723 | $0.00723 |
| Sonnet 5 | $0.00289 | $0.00289 |
| Haiku 4.5 | $0.00145 | $0.00145 |
Grade A, and why
claude-plugin-sdd CLAUDE.md 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 yesterday.
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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Context
This project uses the SDD plugin for architecture governance.
- Architecture Decision Records are in
docs/adrs/ - Specifications are in
docs/openspec/specs/
SDD Skills
| Skill | Purpose |
|---|---|
/sdd:adr |
Create a new Architecture Decision Record |
/sdd:spec |
Create a new specification |
/sdd:list |
List all ADRs and specs with status |
/sdd:status |
Update the status of an ADR or spec |
/sdd:docs |
Generate a documentation site |
/sdd:init |
Set up CLAUDE.md with architecture context |
/sdd:prime |
Load architecture context into session |
/sdd:check |
Quick-check code against ADRs and specs for drift |
/sdd:audit |
Comprehensive design artifact alignment audit |
/sdd:discover |
Discover implicit architecture from existing code |
/sdd:plan |
Break a spec into trackable issues with project grouping and branch conventions |
/sdd:organize |
Retroactively group issues into tracker-native projects |
/sdd:enrich |
Add branch naming and PR conventions to existing issues |
/sdd:work |
Pick up tracker issues and implement them in parallel using git worktrees |
/sdd:review |
Review and merge PRs using reviewer-responder agent pairs |
/sdd:respond |
Address review feedback on a PR: make the code fixes, push, and reply to each thread |
/sdd:graph |
Build and query the artifact graph (validate, impact, ancestors, chain, orphans, cycles, backfill) |
/sdd:index |
Index ADRs, specs, and code into qmd collections for hybrid semantic search |
/sdd:report-friction |
File a feedback issue against the SDD plugin when one of its skills caused significant churn |
Run /sdd:prime [topic] at the start of a session to load relevant ADRs and specs into context.
Governing Comments
When implementing code governed by ADRs or specs, leave comments referencing the governing artifacts:
// Governing: ADR-0001 (chose JWT over sessions), SPEC-0003 REQ "Token Validation"
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.
- yesterday Changed · +2 lines · +133 tokens per session a6807590e966
- 5d ago First seen · 90 lines · 1,313 tokens per session scan A 4dbb1de459e1
claude-plugin-sdd CLAUDE.md is an instructions file published in the GitHub repository joestump/claude-plugin-sdd (32 stars, last pushed yesterday), licensed MIT. It adds 1,446 tokens to every session, about $0.0072 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).