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 commands/ashfaqbs/software-dev-ai-claude-toolkit/tddgit 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/commands/ashfaqbs/software-dev-ai-claude-toolkit/tdd)<a href="https://agentmods.dev/commands/ashfaqbs/software-dev-ai-claude-toolkit/tdd"><img src="https://agentmods.dev/badge/commands/ashfaqbs/software-dev-ai-claude-toolkit/tdd.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.00004 | $0.00286 |
| Opus 5 | $0.00002 | $0.00143 |
| Sonnet 5 | $0.00001 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00029 |
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 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.
What it actually says
TDD Workflow
Implement the following using strict TDD: $ARGUMENTS
Process
1. RED — Write Failing Tests First
- Define what the code should do via test cases.
- Cover the happy path, edge cases, and error cases.
- Run tests — they MUST fail. If they pass, the tests are wrong.
2. GREEN — Minimal Implementation
- Write the minimum code to make tests pass.
- No premature optimization. No extra features.
- Run tests — all must pass.
3. IMPROVE — Refactor
- Clean up the implementation while keeping tests green.
- Extract common logic, improve naming, simplify.
- Run tests again — still green.
Stack-Specific Tools
- Java/Spring Boot: JUnit 5 + Mockito. Use
@SpringBootTestfor integration tests, Testcontainers for real DB. - Python/FastAPI: pytest + pytest-asyncio. Use
httpx.AsyncClientfor API tests. - JavaScript: Jest or Vitest. Use
supertestfor Express API tests. React Testing Library for components.
Rules
- Never write implementation before a failing test exists.
- If you're unsure what to test, ask before proceeding.
- Target 80%+ coverage on the 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.
- 4d ago First seen · 35 lines · 4 tokens per session scan A db99357a845b
tdd is a command published in the GitHub repository Ashfaqbs/software-dev-ai-claude-toolkit (24 stars, last pushed 6mo ago), licensed MIT. It adds 4 tokens to every session and 286 once invoked, about $0.0000 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 commands, from other repositories
tdd-refactor
TDDのRefactorフェーズを実行します。テストを通す実装が完了した後、コード品質の改善とリファクタリングを行います。.
tdd-requirements
TDD開発の要件整理を行います。機能要件を明確化し、テスト駆動開発のための準備を行います。.
spec-impl
Execute spec tasks using TDD methodology.
pm-auto-design2dev
設計レビューから実装完了まで完全自動化（設計レビュー→作業計画→TDD実装）.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.