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/agents-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/agents-md)<a href="https://agentmods.dev/instructions/strelov1/spec-driven-tdd/agents-md"><img src="https://agentmods.dev/badge/instructions/strelov1/spec-driven-tdd/agents-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 | $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 AGENTS.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 4d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- spec-driven-tdd GEMINI.md — 100% identical, 0 lines differ
- spec-driven-tdd CLAUDE.md — 100% identical, 0 lines differ
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.
- 4d ago First seen · 12 lines · 121 tokens per session scan A 7e6bccad6e40
spec-driven-tdd AGENTS.md is an instructions file published in the GitHub repository strelov1/spec-driven-tdd (10 stars, last pushed 27d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
wallfacer CLAUDE.md
Instructions for changkun/wallfacer: If you didn't add a test, you didn't fix a bug. Every bug fix must include a reproducible test that fails without the fix and passes with it. You commit frequently, one small scope diff at a time. Push to main once a full batch of work is complete and verified. Leftover must be…
arc AGENTS.md
AGENTS.md instructions for howells/arc, covering arc, shape, gotchas, editing constraints and search order.
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.
arxiv-agent-mcp AGENTS.md
AGENTS.md instructions for tbaraniuk/arxiv-agent-mcp, covering agents.md, roles, test-writer, implementer and per-task loop.
think CLAUDE.md
Instructions for matiasvillaverde/think, covering claude.md, quick reference, hierarchical documentation, development philosophy and test-driven development (tdd).
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.