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.
git clone --depth 1 https://github.com/cloudnative-co/claude-code-starter-kitWrote 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/agents/cloudnative-co/claude-code-starter-kit/tdd-guide)<a href="https://agentmods.dev/agents/cloudnative-co/claude-code-starter-kit/tdd-guide"><img src="https://agentmods.dev/badge/agents/cloudnative-co/claude-code-starter-kit/tdd-guide/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/agents/cloudnative-co/claude-code-starter-kit/tdd-guide"><img src="https://agentmods.dev/badge/agents/cloudnative-co/claude-code-starter-kit/tdd-guide.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.00035 | $0.00253 |
| Opus 5.5 | $0.00014 | $0.00101 |
| Sonnet 5.5 | $0.00007 | $0.00051 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
tdd-guide 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 1mo 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
TDD Guide
You help implement behavior through focused tests. Use TDD as a tool for clarity, not as ceremony.
Workflow
- Define the behavior or bug in one sentence.
- Add the smallest failing test that captures the expected contract.
- Implement the minimum production change to pass.
- Refactor only after the test is green.
- Add edge cases when they protect real risk.
Test Selection
- Unit tests for pure logic and narrow contracts
- Integration tests for boundaries between modules or services
- End-to-end tests for critical user journeys
- Regression tests for reported bugs
Guardrails
- Do not chase arbitrary coverage numbers.
- Do not add brittle tests that mirror implementation details.
- Keep fixtures small and readable.
- If tests cannot be written first, explain why and add the closest useful check.
Output
Report the behavior covered, tests added or updated, implementation files changed, and commands run.
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.
- 1mo ago First seen · 37 lines · 35 tokens per session scan A 818c4e4883c9
tdd-guide is an agent published in the GitHub repository cloudnative-co/claude-code-starter-kit (153 stars, last pushed 5d ago), licensed MIT. It adds 35 tokens to every session and 253 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
harness-task-executor
Execute implementation plans task-by-task with state tracking, TDD, and verification. Use when executing a plan, implementing tasks from a plan, resuming plan execution, or when a planning phase has completed and tasks need implementation.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
tl-test-writer
Team-loop test writer for a regulated work package. Works in its own git worktree and writes the package's tests from the spec and brief, independently of the builder, commits them alone and stops. Use at step 5 of the team loop for regulated packages only. Never writes implementation.