Borrowing it
Nothing to install: this file belongs to viamus/claude-sdd-plugin. 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/viamus/claude-sdd-plugin/main/CLAUDE.mdgit 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/instructions/viamus/claude-sdd-plugin/claude-md)<a href="https://agentmods.dev/instructions/viamus/claude-sdd-plugin/claude-md"><img src="https://agentmods.dev/badge/instructions/viamus/claude-sdd-plugin/claude-md/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/instructions/viamus/claude-sdd-plugin/claude-md"><img src="https://agentmods.dev/badge/instructions/viamus/claude-sdd-plugin/claude-md.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.00570 | $0.00570 |
| Opus 5.5 | $0.00228 | $0.00228 |
| Sonnet 5.5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
claude-sdd-plugin 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 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Orchestrator — Plugin Context
This project uses Spec-Driven Design (SDD). Code should only be generated after an approved specification.
Fundamental Rules
- Spec-First: Never generate implementation code without a corresponding approved spec in
specs/. Always ask: "Which approved spec am I following?" - Contract Fidelity: Generated code must implement EXACTLY what the spec defines — no more, no less. Do not add features, parameters, or behaviors that are not in the spec.
- Error Coverage: Every error scenario defined in the spec MUST have corresponding handling in the code.
- No Hallucination: If the spec does not define a behavior for a specific case, ask the developer instead of making it up.
Workflow
/sdd:sdd-init <name>— Creates a new spec from the template/sdd:sdd-learn <name> <sources>— Ingests docs, files, or web pages into spec context/sdd:sdd-build <name>— Builds the spec via guided conversation (auto-loads knowledge)/sdd:sdd-review— Validates whether the spec is complete/sdd:sdd-gen— Full pipeline: generate code + consistency check + quality audit + deliver/sdd:sdd-status— Shows the state of all specs and dependency graph
Pipeline (automated by sdd-gen)
Generate → Consistency Check → Quality Audit → Deliver
↑ auto-fix ↑ auto-fix
Check and audit are internal steps — the user only runs /sdd:sdd-gen.
Plugin Structure
claude-sdd-plugin/
├── .claude-plugin/
│ ├── plugin.json # Plugin manifest
│ └── marketplace.json # Marketplace catalog
├── skills/
│ ├── sdd-init/SKILL.md # Create spec
│ ├── sdd-learn/SKILL.md # Ingest knowledge for specs
│ ├── sdd-build/SKILL.md # Build spec via conversation
│ ├── sdd-review/SKILL.md # Validate spec
│ ├── sdd-gen/SKILL.md # Full pipeline
│ ├── sdd-check/SKILL.md # (internal) Consistency check
│ ├── sdd-audit/SKILL.md # (internal) Quality audit
│ └── sdd-status/SKILL.md # Status + dependency graph
├── templates/
│ └── spec-template.md
└── docs/
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 · 50 lines · 570 tokens per session scan A 3f6a2791b023
claude-sdd-plugin CLAUDE.md is an instructions file published in the GitHub repository viamus/claude-sdd-plugin (4 stars, last pushed 6mo ago), licensed MIT. It adds 570 tokens to every session, about $0.0023 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 instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.