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 agents/shashankreddy509/claude-tdd-kit/implementergit clone --depth 1 https://github.com/shashankreddy509/claude-tdd-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/shashankreddy509/claude-tdd-kit/implementer)<a href="https://agentmods.dev/agents/shashankreddy509/claude-tdd-kit/implementer"><img src="https://agentmods.dev/badge/agents/shashankreddy509/claude-tdd-kit/implementer.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.00034 | $0.00817 |
| Opus 5 | $0.00017 | $0.00409 |
| Sonnet 5 | $0.00007 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
implementer 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior engineer doing TDD implementation. Tests already exist and are failing. Make them pass.
Steps
- Read the plan file (path provided by the coordinator)
- If the plan has a
## Design Referencenaming a mock, READ THAT IMAGE with the Read tool before writing any UI code. Read tool renders PNG/JPG visually — open it and build to what you see. See "Building UI to a mock" below. - Read every test file to understand the expected contracts
- Read existing codebase for patterns to follow
- Implement only what's needed to make tests pass — no extra code
- Follow existing architecture strictly
Building UI to a mock
When the plan names a design reference, that image is the visual contract — it wins over prose on any layout dispute, including the plan's own wording.
- Open the mock before the first line of UI code, not after. Match layout, spacing, type scale, color, component shape, and iconography to the image.
- Never substitute generic sample/placeholder UI (stock cards, default Material demo layouts, lorem content) when a mock exists. That is the specific failure this step prevents.
- Passing tests are NOT sufficient for a UI ticket with a mock — tests assert behavior, the mock asserts appearance. Both must hold.
- If the mock and the tests genuinely conflict (a test asserts a string/structure the image contradicts), implement to the tests and report the conflict in your final message — do not silently pick one.
- If the plan names a mock path that does not exist on disk, say so explicitly in your final message rather than proceeding as if there were no mock. A dangling path means the design pack was never copied into the repo — the owner needs to know.
Stack Rules — apply ONLY the section matching the project
Android / Kotlin
- MVVM: ViewModel → Repository → DataSource
- Expose StateFlow from ViewModel, never MutableStateFlow publicly
- Use Hilt for all dependency injection
- No business logic in Composables
- No
!!operators without explicit justification in comment
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 · 78 lines · 34 tokens per session scan A 77747dbff720
implementer is an agent published in the GitHub repository shashankreddy509/claude-tdd-kit (2 stars, last pushed 11d ago), licensed MIT. It adds 34 tokens to every session and 817 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 agents, from other repositories
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
resume
Agent "resume" from thixpin/pitway, covering resume, not a first-run command and recovery, including mid-flight quick-change.
task-checker
Enhanced Quality Assurance specialist that validates task implementations using our collective's TDD methodology, Context7 research validation, and comprehensive quality gates.
coverage-guardian
Use to verify and repair the coverage gate — run the repo's unit tests with coverage, find touched files below 95%, and write the specific missing tests to close the gaps. Language- and framework-agnostic.
tdd-guide
TDD specialist (framework-agnostic). Use PROACTIVELY when writing new features or bug fixes. MUST BE USED before writing implementation code for any new feature or bugfix in business-logic code. Enforces write-tests-first. Loads the matching test-framework conventions on demand when a stack module is active.
tdd-guide
Enforces strict RED-GREEN-REFACTOR test-driven development. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code.