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/strelov1/spec-driven-tdd/claude-mdgit clone --depth 1 https://github.com/strelov1/spec-driven-tddWrote 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/strelov1/spec-driven-tdd/claude-md)<a href="https://agentmods.dev/instructions/strelov1/spec-driven-tdd/claude-md"><img src="https://agentmods.dev/badge/instructions/strelov1/spec-driven-tdd/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.00121 | $0.00121 |
| Opus 5 | $0.00060 | $0.00060 |
| Sonnet 5 | $0.00024 | $0.00024 |
| Haiku 4.5 | $0.00012 | $0.00012 |
Grade A, and why
spec-driven-tdd 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 6d 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.
This is a copy
100% identical to spec-driven-tdd AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
spec-driven-tdd
This repo is a skill-pack. When implementing an OpenSpec change, invoke the
spec-driven-tdd skill and follow its lifecycle: plan in OpenSpec, isolate in a
worktree, implement each task via TDD → simplify → review, then finish + archive.
See skills/spec-driven-tdd/SKILL.md for the full workflow and
docs/dependencies.md for what must be installed.
Keep responses focused, brief, and concise. Spend most of the response on the outcome, not on narrating steps already taken.
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.
- 6d ago First seen · 12 lines · 121 tokens per session scan A 7e6bccad6e40
spec-driven-tdd CLAUDE.md is an instructions file published in the GitHub repository strelov1/spec-driven-tdd (10 stars, last pushed 29d ago), licensed MIT. It adds 121 tokens to every session, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to spec-driven-tdd AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
sgcop CLAUDE.md
Claude Code instructions for SonicGarden/sgcop, covering sgcop, コマンド, アーキテクチャ, 新しい cop を追加する手順 and cop のテスト記述.
digital-service-orchestra skills.instructions.md
Instructions for navapbc/digital-service-orchestra, a project described as: Workflow infrastructure plugin for Claude Code projects — TDD-driven sprint management, review gates, hook parameterization, and multi-stack config.
mcp-repo-onboarding AGENTS.md
Instructions for rogermt/mcp-repo-onboarding, covering agents.md — agent & copilot instructions, current status, output verification, project identity and ⚠️ critical: tdd required.
speckit AGENTS.md
AGENTS.md instructions for jmanhype/speckit, covering agents.md - instructions for ai coding agents, core philosophy, pivotal methodology alignment, pivotal-style epic format and priority levels (pivotal-aligned).
arxiv-agent-mcp AGENTS.md
AGENTS.md instructions for tbaraniuk/arxiv-agent-mcp, covering agents.md, roles, test-writer, implementer and per-task loop.
opencode-copilot-instructions AGENTS.md
AGENTS.md instructions for ekroon/opencode-copilot-instructions, covering agent instructions, orchestration pattern, 1. always orchestrate (unless being orchestrated), 2. test-driven development (tdd) and tdd workflow for each module.