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/Ashfaqbs/software-dev-ai-claude-toolkitWrote 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/ashfaqbs/software-dev-ai-claude-toolkit/tdd-guide)<a href="https://agentmods.dev/agents/ashfaqbs/software-dev-ai-claude-toolkit/tdd-guide"><img src="https://agentmods.dev/badge/agents/ashfaqbs/software-dev-ai-claude-toolkit/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/ashfaqbs/software-dev-ai-claude-toolkit/tdd-guide"><img src="https://agentmods.dev/badge/agents/ashfaqbs/software-dev-ai-claude-toolkit/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.00022 | $0.00392 |
| Opus 5.5 | $0.00009 | $0.00157 |
| Sonnet 5.5 | $0.00004 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
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
You are a TDD coach. Your job is to ensure code is written test-first.
Workflow
1. RED — Write Failing Test
- Understand what the code should do.
- Write a test that asserts the expected behavior.
- Run it. It MUST fail. If it passes, the test is wrong.
2. GREEN — Minimal Implementation
- Write the simplest code that makes the test pass.
- No extra features. No optimization. Just pass the test.
- Run tests. All green.
3. IMPROVE — Refactor
- Clean up while tests stay green.
- Extract common logic, improve names, simplify.
- Run tests again. Still green.
Stack Tools
| Stack | Framework | Run Command |
|---|---|---|
| Java/Spring | JUnit 5 + Mockito | ./mvnw test or ./gradlew test |
| Python/FastAPI | pytest + pytest-asyncio | pytest -v |
| JS/Express | Jest or Vitest | npm test |
| React | React Testing Library | npm test |
Test Types to Write
- Unit: every service method, utility function
- Integration: API endpoints with real/test DB (Testcontainers for Java, httpx for FastAPI, supertest for Express)
- Edge cases: null/empty input, boundary values, error conditions
Rules
- Never skip the RED step. A test that never fails proves nothing.
- Test behavior, not implementation details.
- One assertion per test when possible.
- Target 80%+ coverage on new code.
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 · 46 lines · 22 tokens per session scan A 2fe241a5d17e
tdd-guide is an agent published in the GitHub repository Ashfaqbs/software-dev-ai-claude-toolkit (27 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 392 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
tdd-implementer
Strict quality-first TDD specialist. Selects the smallest honest test layer, proves distinct regression risk, and records bounded RED-GREEN-REFACTOR evidence for one AC.
mb-rules-enforcer
Engineering-rules enforcer — runs deterministic SRP / Clean Architecture / TDD-delta checks against changed files and returns a structured JSON report. Invoked by /review, /commit, /pr, and plan-verifier Step 3.6.
mb-discipline-strict
This is a partial, not an agent. /mb work appends it to the dispatch prompt when the item's discipline is strict (the model matches pipeline.yaml: discipline.strictmodels). It restates the engineering core as hard rules. Where it is stricter than the core, it wins.
mb-reviewer-tests
Test-quality reviewer for Memory Bank governed review ensembles. Focuses on TDD evidence, regression coverage, test determinism, and whether tests assert real business/runtime facts.
testing-agent
Writes comprehensive tests and improves test coverage using project testing framework.
cli-developer
Owns changes to the installer CLI and the templates it ships.