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 skills/strelov1/spec-driven-tdd/using-spec-driven-tddnpx skills add strelov1/spec-driven-tdd --skill using-spec-driven-tddgit 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/skills/strelov1/spec-driven-tdd/using-spec-driven-tdd)<a href="https://agentmods.dev/skills/strelov1/spec-driven-tdd/using-spec-driven-tdd"><img src="https://agentmods.dev/badge/skills/strelov1/spec-driven-tdd/using-spec-driven-tdd.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.00044 | $0.00303 |
| Opus 5 | $0.00022 | $0.00151 |
| Sonnet 5 | $0.00009 | $0.00061 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
using-spec-driven-tdd 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 5d 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.
What it actually says
Using spec-driven-tdd
You have the spec-driven-tdd workflow: plan and track in OpenSpec, implement with Superpowers discipline (TDD, simplify, review), finish and archive.
The rule
When you are about to implement an OpenSpec change — or the user asks to build,
apply, or work through a change — invoke the spec-driven-tdd skill BEFORE
writing code, and follow its steps rather than improvising.
If a 1% chance it applies, invoke it. Knowing the lifecycle is not the same as following it.
What it composes
- Plan / track: OpenSpec (
/opsx:propose,/opsx:apply,/opsx:archive,/opsx:sync). - Execute: Superpowers (
test-driven-development,requesting-code-review,receiving-code-review,systematic-debugging,using-git-worktrees,verification-before-completion,finishing-a-development-branch) plus this pack'ssimplifyskill.
Dependencies and graceful degradation: see docs/dependencies.md.
Invoke spec-driven-tdd now if you are starting implementation.
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.
- 5d ago First seen · 32 lines · 44 tokens per session scan A 031a0caa1b0c
using-spec-driven-tdd is a skill published in the GitHub repository strelov1/spec-driven-tdd (10 stars, last pushed 28d ago), licensed MIT. It adds 44 tokens to every session and 303 once invoked, about $0.0002 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 skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.