Borrowing it
Nothing to install: this file belongs to danweinerdev/claude-sdd-planner. 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/danweinerdev/claude-sdd-planner/main/CLAUDE.mdgit clone --depth 1 https://github.com/danweinerdev/claude-sdd-plannerWrote 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/danweinerdev/claude-sdd-planner/claude-md)<a href="https://agentmods.dev/instructions/danweinerdev/claude-sdd-planner/claude-md"><img src="https://agentmods.dev/badge/instructions/danweinerdev/claude-sdd-planner/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/danweinerdev/claude-sdd-planner/claude-md"><img src="https://agentmods.dev/badge/instructions/danweinerdev/claude-sdd-planner/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.06158 | $0.06158 |
| Opus 5.5 | $0.02463 | $0.02463 |
| Sonnet 5.5 | $0.01232 | $0.01232 |
| Haiku 4.5 | $0.00616 | $0.00616 |
Grade A, and why
claude-sdd-planner 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Planner
A spec-driven development toolchain: structured project planning with lifecycle skills, intent-isolated review agents, and a deterministic Go validator (sdd). This repository is the single source for every supported harness:
- Repo root — the canonical, hand-edited Claude Code plugin (
commands/,agents/,skills/,shared/,hooks/). .codex-plugin/and.opencode-plugin/— generated plugin trees for Codex and OpenCode, produced bysdd plugin sync. Never hand-edited; drift failsmake test.
Directory Structure
claude-sdd-planner/ # Repository root = canonical Claude plugin root
├── .claude-plugin/
│ └── plugin.json # Canonical manifest — single source of version + minSddVersion
├── commands/ # Slash commands (auto-namespaced /sdd-planner:*); each is a dir with SKILL.md
│ └── <name>/SKILL.portable.md # optional hand-maintained portable variant (code-review, implement, setup)
├── skills/ # Model-only reference skills (auto-loaded by description, not /-invocable)
│ ├── <lang>-specifications/ # per-language structural verification (cpp, rust, go, python, typescript, java, swift)
│ ├── decision-log/ # ad-hoc plan-decision capture outside lifecycle skills
│ ├── sdd-cli/ # how to drive the sdd binary — task→command map + write-path discipline
│ └── test-{design,generate,assess}/ # composed test-quality instruction skills
├── agents/ # Subagent definitions — also the source for the portable role prompts
├── hooks/ # Wrappers that locate the binary; hooks.json is NOT shipped —
│ ├── sdd-hook.sh # `sdd provision` generates it per-platform (see below)
│ └── sdd-hook.ps1
├── shared/ # Conventions + templates, shipped to every harness
│ ├── frontmatter-schema.md # single source of truth for artifact metadata
│ ├── completion-evidence.md # evidence-gated completion — what `complete` requires, per level
│ ├── decision-log.md # plan decisions — per-plan JSON file, entry schema, write protocol
│ ├── decision-framework.md # universal decision discipline for all skills and agents
│ ├── path-resolution.md # planning-root / plugin-dir / target-repo resolution (marker-managed)
│ ├── orchestration.md # orchestration model + portable prompt catalog (marker-managed)
│ ├── vcs-detection.md # VCS detection algorithm + operations table (git / p4 / plain)
│ ├── autonomy.md # cross-skill autonomy table — what runs solo vs stops for the user
│ ├── review-lanes.md # project-supplied review-lane socket (+ .portable.md variant)
│ ├── review-artifacts.md # persisted review contract incl. the phase-completion gate
│ ├── language-verification.md # language-specific verification — what good looks like
│ ├── agent-runtime.md # portable runtime conventions (resolution, delegation, resource boundary)
│ └── templates/ # document templates (+ agents-md-*, claude-md-*, custom-reviewer variants)
├── cmd/sdd/ # The `sdd` binary — validation, artifact writes, hooks, plugin sync
├── internal/ # Binary internals (rules, decisions, compile, hook, provision, schema, vcs, portable)
├── tools/ # genfixtures + the frozen regression corpus (run by `go test ./...`)
├── .codex-plugin/ # GENERATED Codex plugin tree — never hand-edit
├── .opencode-plugin/ # GENERATED OpenCode plugin tree (same content) — never hand-edit
├── portable-overrides/ # Hand-maintained portable-only sources (the portable README)
├── .plans/ # This repo's own planning artifacts (planning-config.json → ".plans")
│ └── Plans/<Name>/<Name>-Decisions.json # per-plan decisions — pd-<hex> entries are standing constraints
├── Makefile # build / test / plugins / bump-*
└── bump-version.py # patch|minor|major bumps, `set X.Y.Z`, `set-floor X.Y.Z`
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 Changed · +9 lines · +519 tokens per session 843e5cf44179
- 1mo ago Changed · -139 tokens per session ca81c30bfdc2
- 1mo ago Changed · +10 tokens per session 71e433468092
- 1mo ago Changed · +239 tokens per session 58cb738736d0
- 1mo ago First seen · 219 lines · 5,529 tokens per session scan A 563f47e6f80e
claude-sdd-planner CLAUDE.md is an instructions file published in the GitHub repository danweinerdev/claude-sdd-planner (2 stars, last pushed 25d ago), licensed MIT. It adds 6,158 tokens to every session, about $0.0246 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.