spec-driven-development: Instructions file for Claude Code

CLAUDE.md

spec-driven-development CLAUDE.md is an instructions file for Claude Code from voro6yov/spec-driven-development. It costs 4,763 tokens per session, scanned B, original, Apache-2.0.

Repository instructions for a Claude Code plugin marketplace focused on spec-driven development. It documents how plugins generate domain specifications from Mermaid diagrams and implement them with unit tests.

In plain words
What is it for?
Use it when developing or maintaining the marketplace, its plugin manifests, skills, agents, or domain-spec pipeline. It also guides work with the shared Python reference modules for entities, value objects, validation rules, and persistence.
Why use it?
It gives Claude Code the repository’s layout, shared conventions, and workflow so changes follow the project’s intended structure. It also clarifies that the repository contains runtime-loaded Markdown artifacts rather than an application.

Instructions file for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: mentions .claude-plugin; mentions CLAUDE.md; mentions subagents.

This is voro6yov/spec-driven-development's own configuration. It tells Claude Code how to work on spec-driven-development itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything spec-driven-development configures →

Runs only inside a plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else, and the catalogue could not identify which plugin ships it.

Reuse

Borrowing it

Nothing to install: this file belongs to voro6yov/spec-driven-development. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/voro6yov/spec-driven-development/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/voro6yov/spec-driven-development

Made for: Claude Code.

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

agentmods badge for spec-driven-development CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/voro6yov/spec-driven-development/claude-md/github.svg)](https://agentmods.dev/instructions/voro6yov/spec-driven-development/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/voro6yov/spec-driven-development/claude-md"><img src="https://agentmods.dev/badge/instructions/voro6yov/spec-driven-development/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.

agentmods 80×15 button for spec-driven-development CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/voro6yov/spec-driven-development/claude-md"><img src="https://agentmods.dev/badge/instructions/voro6yov/spec-driven-development/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 4,763 This file is loaded in full into every session.
When invoked 4,763 The same file — it is already loaded in full.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.04763 $0.04763
Opus 5.5 $0.01905 $0.01905
Sonnet 5.5 $0.00953 $0.00953
Haiku 4.5 $0.00476 $0.00476

Measured 1mo ago against content hash cbe4a1ff85e4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

spec-driven-development CLAUDE.md scanned grade B with 1 finding 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

- **The copied reference modules, `spec-core:modules`** — the umbrella home of the **runtime-contract Python modules** the spec pipeline copies verbatim into the target repo during init/scaffold: `shared/` (domain primit
CLAUDE.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Repository purpose

This is a Claude Code plugin marketplace (.claude-plugin/marketplace.json) for spec-driven development plugins, e.g.:

  • plugins/domain-spec — generates DDD class specs from a Mermaid class diagram, then implements the domain package and its unit tests
  • plugins/project-scaffold — /project-scaffold:new-service renders a new service repo with a deterministic stdlib script (skills/new-service/scaffold.py + templates/), not an LLM: the keystone containers.py / settings.py / constants.py / entrypoint.py / __main__.py shells every /init-* skill and integrator patches into, plus Docker/compose/Liquibase and the vendored spec-core modules. When a plugin agent changes an anchor it inserts after (a container attribute, an entrypoint.py function, a conftest fixture), update the matching template and re-render all 8 layer-flag combinations (--no-persistence/--no-rest/--no-messaging) through make check.

There is no application code, no build step, and no test suite. Artifacts are Markdown — skills, agent definitions, and plugin manifests — that are loaded by Claude Code at runtime.

Plugin layout

Each plugin under plugins/<name>/ has:

  • .claude-plugin/plugin.json — plugin manifest with version (bump on user-visible changes)
  • agents/*.md — single-purpose subagents with frontmatter (name, description, tools, optional model)
  • skills/<skill>/SKILL.md — reusable skills; umbrella orchestrator skills (e.g. generate-domain) chain agent orchestrators (specs-generator, code-generator), which in turn coordinate the worker agents

plugins/spec-core/skills/modules/ contains Python reference modules (Entity, ValueObject, guards, the persistence context packages, the REST serializers, etc.) that the generated code imports — not source for this repo to test, but the runtime contract that the implementers/scaffolders target and copy verbatim into the target repo. They are homed under the spec-core:modules umbrella skill; see the spec-core section below for the resolution mechanism.

Read the full file on GitHub · 64 lines

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. 1mo ago Changed · +1 lines · +263 tokens per session cbe4a1ff85e4
  2. 2mo ago First seen · 63 lines · 4,500 tokens per session scan B 5b4e539be00f

Subscribe to this mod's changes

spec-driven-development CLAUDE.md is an instructions file published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 4,763 tokens to every session, about $0.0191 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

spec-driven-development CLAUDE.md compared with instructions from other repositories

spec-driven-development CLAUDE.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
spec-driven-development CLAUDE.mdvoro6yov/spec-driven-developmentInstructions file51mo agoApache-2.0B4,763Claude Code
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode