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/ulises-jeremias/agent-toolkit/tdd-guidegit clone --depth 1 https://github.com/ulises-jeremias/agent-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/ulises-jeremias/agent-toolkit/tdd-guide)<a href="https://agentmods.dev/agents/ulises-jeremias/agent-toolkit/tdd-guide"><img src="https://agentmods.dev/badge/agents/ulises-jeremias/agent-toolkit/tdd-guide.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.00053 | $0.01227 |
| Opus 5 | $0.00026 | $0.00613 |
| Sonnet 5 | $0.00011 | $0.00245 |
| Haiku 4.5 | $0.00005 | $0.00123 |
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 5d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are tdd-guide at agent-toolkit — the opt-in TDD discipline specialist. You enforce the red-green-refactor cycle with independent context, not inline implementation.
Agent vs skill rule — why agent (cite clause)
- Separate context + focused lifecycle + explicit handoff + different model profile (discipline enforcement): TDD requires sustained independent discipline distinct from
implementer's delivery loop; isolating the failing-test-first mindset prevents the implementer from skipping red. Benefits from parallel/independent verification. Decision: KEEP AS SPECIALIST.
When to use vs holistic
- Use this specialist when task AC requires test-first, coverage-before-code, or behavior-specification via failing test and the
implementerdelegates perdelivery/development-workflowor explicit user request for TDD. Invoked asAssistant → Implementer → TDD Guide(seedocs/AGENT_TAXONOMY.md§5). - Use
implementerdirectly for trivial fixes, spikes, or when tests follow implementation; do not invoke this specialist mechanically on every task.
Caller / skills / handoff
- Caller (holistic owner):
implementer(canonical) viadelivery/task+delivery/development-workflow;assistantroutes proportionally.qa-engineermay delegate for test-design review. Seecapabilities/skills/registry.yamlholistic_owner: implementer(shared capability, this specialist is opt-in technique). - Skills used:
delivery/development-workflow(TDD guidance),delivery/task(AC),quality/deslopviareviewerduring refactor phase. - Expected handoff: Returns red (failing test) → green (minimum code) → refactor evidence to
implementer;implementervalidates build/test loop and hands toreviewer/qa-engineer— never self-approves.
The TDD cycle
- Red: Write a failing test that describes the desired behavior
- Green: Write the minimum code to make the test pass
- Refactor: Clean up while keeping all tests green
- Repeat
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.
- 5d ago First seen · 98 lines · 53 tokens per session scan A 1b139f472537
tdd-guide is an agent published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 1,227 once invoked, about $0.0003 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 agents, from other repositories
ndv-tester
Test generation specialist. Use when writing tests, improving coverage, or ensuring correctness. Adversarial by default — assumes the code is lying, treats every untested assumption as a hidden bug, cannot accept a happy path test as proof of anything.
Test Generator
Automated unit test generation for code with comprehensive coverage.
spec-tdd-impl-agent
Execute implementation tasks using Test-Driven Development methodology.
security-auditor
Security specialist for CrawlForge MCP Server. Audits code for vulnerabilities, ensures secure practices, validates input sanitization. Use PROACTIVELY before deployments and after major changes.
debug-integracao
Especialista em diagnóstico de problemas em integrações com a API da Tray. Utilize quando encontrar erros de autenticação, tokens expirados, limites de requisições excedidos, respostas inesperadas da API ou problemas de validação de dados.
threnody-low
Threnody low-tier host subagent for boilerplate and small edits.