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 skills add emaraschio/cursor-commands --skill tddgit clone --depth 1 https://github.com/emaraschio/cursor-commandsWrote 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/emaraschio/cursor-commands/tdd)<a href="https://agentmods.dev/skills/emaraschio/cursor-commands/tdd"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/tdd/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.
<a href="https://agentmods.dev/skills/emaraschio/cursor-commands/tdd"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/tdd.svg" alt="Reviewed on agentmods" width="80" 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.00068 | $0.01366 |
| Opus 5 | $0.00034 | $0.00683 |
| Sonnet 5 | $0.00014 | $0.00273 |
| Haiku 4.5 | $0.00007 | $0.00137 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-driven development
Role
You guide a specify → encode → fulfill session (Canon TDD): turn agreed specifications into executable tests one at a time, then write only enough production code to make the current failure go away. The user approves each test and each behavior commit. You do not batch-write tests or ship with a dirty test suite.
When to use
Use when the user invokes /tdd with a draft behavior specification. For broad test coverage without the red-green loop, use write-unit-tests. For full feature delivery from a requirement, use requirement-to-implementation. For fixing a broken suite without new behavior, use run-all-tests-and-fix.
Initial specification
Take the initial specification from the user's message (draft scenarios, examples, or file references). If missing, ask one focused question before proceeding.
Specify-encode-fulfill
At session level:
- Specify: agree what to build as concrete scenarios.
- Encode: turn each scenario into one automated test (executable specification).
- Fulfill: write production code so the current test passes.
At fine grain (repeat until the specification list is empty):
- Maintain a numbered specification list for this session.
- Encode exactly one test per cycle: one list item as a failing automated test.
- Fulfill with code just barely enough to make that failure go away, no speculative coding.
- Commit the behavior change before any refactor; never mix behavior changes with refactoring in one commit.
- Optionally refactor after the behavior commit, with user approval.
- Return to step 2 for the next list item.
Reference: Canon TDD (Kent Beck).
Clarifying specifications
Before writing tests:
- Repeat the specifications in your own words (scenario form: under scenario A, X happens; under scenario B, Y happens).
- Ask the user to confirm or correct.
- If confirmed, proceed; otherwise revise and repeat from step 1.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 129 lines · 68 tokens per session scan A 8665bb825e11
tdd is a skill published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 1,366 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
ijfw-tdd
RED-GREEN-REFACTOR enforcement. Use when implementing a feature or bugfix before writing implementation code. Trigger: tdd, test first, red green refactor, /ijfw-tdd.
hotfix
Fixes an observed defect with reproducible evidence in one call: writes a short trace doc before touching code, implements the fix, and backs it with a regression test written before the fix. Production incidents are the motivating case, not a gate. When blocked, it halts by name and saves the doc for a later call to…
write-plan
Write a bite-sized TDD implementation plan from a spec before touching code. Saves under docs/plans/ / (gitignored WIP); promote to docs/features/ / when stable. Use when the user invokes write-plan, or when interview-plan hands off an assembled spec. Do not use to implement.
subagent-driven-development
Orchestrating sub-agents through TDD phases for complex features.
test-driven-development
Red-green-refactor TDD implementation cycle.
writing-plans
Convert test scenarios into ordered implementation plans for TDD.