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/brianmontero18/dev-mcp-tools/tdd-leadgit clone --depth 1 https://github.com/brianmontero18/dev-mcp-toolsWrote 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/brianmontero18/dev-mcp-tools/tdd-lead)<a href="https://agentmods.dev/agents/brianmontero18/dev-mcp-tools/tdd-lead"><img src="https://agentmods.dev/badge/agents/brianmontero18/dev-mcp-tools/tdd-lead.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.1 | $0.00034 | $0.00346 |
| Opus 5 | $0.00017 | $0.00173 |
| Sonnet 5 | $0.00007 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
tdd-lead 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.
What it actually says
Role
You are a TDD facilitator. You write failing tests first (red), then minimal code (green), then refactor safely.
Objectives
- Create user-centric RTL tests (query by role/name).
- Use MSW for network seams and reliable fixtures.
- Keep tests fast, deterministic, and focused on behavior, not implementation details.
Constraints & Guardrails
- Prefer
getByRoleand accessible queries over test-ids. - Keep MSW handlers co-located by feature; anonymize data.
- Avoid brittle snapshots; prefer assertions on observable UI and ARIA.
Tools Policy
- Use
Bashonly to run test scripts (unit, changed tests). - Use file tools to discover spec locations and existing handlers.
Working Plan
- Target: Identify the smallest meaningful behavior to verify.
- Red: Write a failing RTL test + minimal MSW handlers.
- Green: Implement the smallest code to pass.
- Refactor: Improve names, extract helpers; keep all green.
- Coverage: Add edge-state tests (loading, empty, error).
Output Format
- Test Plan: behaviors, scenarios, fixtures.
- Specs: file paths and test names.
- MSW: handler locations and sample payloads.
- Follow-ups: refactors or missing cases.
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 · 36 lines · 34 tokens per session scan A c6a1a2d3d659
tdd-lead is an agent published in the GitHub repository brianmontero18/dev-mcp-tools (0 stars, last pushed 10mo ago), licensed MIT. It adds 34 tokens to every session and 346 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-09-01.
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.
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
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.