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/stevesolun/ctx/tddnpx skills add stevesolun/ctx --skill tddgit clone --depth 1 https://github.com/stevesolun/ctxWhat 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.00039 | $0.00348 |
| Opus 5 | $0.00019 | $0.00174 |
| Sonnet 5 | $0.00008 | $0.00070 |
| Haiku 4.5 | $0.00004 | $0.00035 |
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 3d 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
Test-Driven Development
Use small red → green → refactor cycles when a test-first feedback loop is practical. Treat repository conventions, existing tests, and the requested behavior as authoritative.
Loop
- Identify one observable behavior and the seam through which callers see it.
- Write the smallest meaningful test and confirm that it fails for the expected reason.
- Add only enough implementation to make the test pass.
- Refactor when doing so improves clarity or design; keep the suite green.
- Repeat with the next vertical slice.
Infer seams from public interfaces and nearby tests. Ask the user only when choosing a seam would materially change the product contract, cost, or scope.
Judgment
- Prefer behavior-focused tests that survive internal refactors.
- Derive expected results from a specification, worked example, or other independent source rather than duplicating the implementation.
- Mock external or nondeterministic boundaries when useful; follow established repository patterns where they provide an adequate feedback loop.
- Prefer vertical slices over a speculative batch of tests. Batch closely related mechanical cases when that is clearer and faster.
- If a failing-first cycle is impractical—for example in legacy code with no usable seam—state the limitation and establish the nearest reliable characterization or integration test.
Read tests.md for examples and mocking.md when deciding whether and where to use test doubles.
What ships with it
3 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.
- 3d ago First seen · 39 lines · 39 tokens per session scan A 2d2418a666ff
tdd is a skill published in the GitHub repository stevesolun/ctx (581 stars, last pushed 10d ago), licensed MIT. It adds 39 tokens to every session and 348 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-30.
Other skills, from other repositories
agent-implementer-sparc-coder
Agent skill for implementer-sparc-coder - invoke with $agent-implementer-sparc-coder.
agent-integration
Run all three agent integration phases sequentially: research, write-tests, and implement using E2E-first TDD (unit tests written last). For individual phases, use /agent-integration:research, /agent-integration:write-tests, or /agent-integration:implement. Use when the user says "integrate agent", "add agent…
nv-implement
Implement planned work by fanning out parallel subagents on isolated worktrees — TDD at pre-agreed seams, per-slice nv-park-and-review, merge back, full suite once at the end.
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.
drill-tdd
Use when implementing any feature or bugfix — enforces the Red-Green-Refactor drill with no production code allowed without a failing test first.
the-hit
Use when the execution plan is approved and it is time for parallel execution — dispatches workers through crew leads to implement work packages with TDD enforcement, report collection, and escalation protocols.