spec-driven-development CLAUDE.md

Repository instructions for a spec-driven development plugin, where software changes start from a written specification. They describe its plugin files, the format used when hooks send context to coding tools, and how skills are discovered.

In plain words
What is it for?
Use them when editing the plugin manifest, package metadata, startup or prompt hooks, skill files, or the context passed to Claude Code, Codex, Cursor, and Copilot.
Why use it?
They help keep plugin metadata and hook messages compatible with the tools that load them. They also make sure skills can be found and triggered correctly.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/voytechg/spec-driven-development/claude-md
Clone the repo
git clone --depth 1 https://github.com/VoytechG/spec-driven-development
Per session 207 This file is loaded in full into every session.
When invoked 207 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00207 $0.00207
Opus 5 $0.00103 $0.00103
Sonnet 5 $0.00041 $0.00041
Haiku 4.5 $0.00021 $0.00021

Measured 2d ago against content hash a6829505cedf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

spec-driven-development 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 2d 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.

CLAUDE.md · 16 lines

What it actually says

spec-driven-development — Claude Code Notes

Read AGENTS.md first. This file adds Claude-specific points only.

Manifest

Claude Code reads .claude-plugin/plugin.json and the marketplace listing in .claude-plugin/marketplace.json. Keep both in sync with package.json.

Hook output shape

The hooks/session-start and hooks/user-prompt-submit scripts emit Claude/Codex hookSpecificOutput.additionalContext by default, Cursor additional_context when CURSOR_PLUGIN_ROOT is set, and Copilot's older top-level additionalContext when COPILOT_CLI is set. Do not emit multiple shapes from one hook; hosts can double-inject.

Skill discovery

Skills live under skills/<name>/SKILL.md with YAML frontmatter (name, description). Claude Code's Skill tool surfaces them by name. The description is the trigger phrase the agent matches against — keep it as a one-line "use when ..." cue.

Changes

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.

  1. 2d ago First seen · 16 lines · 207 tokens per session scan A a6829505cedf

Subscribe to this mod's changes

spec-driven-development CLAUDE.md is an instructions file published in the GitHub repository VoytechG/spec-driven-development (4 stars, last pushed 3mo ago), licensed MIT. It adds 207 tokens to every session, about $0.0010 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.

Related

Other instructions, from other repositories

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.

github/spec-kit · 7,104 tokens

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).

microsoft/vscode · 6,785 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens