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/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/rules/ulises-jeremias/agent-toolkit/tdd-guide)<a href="https://agentmods.dev/rules/ulises-jeremias/agent-toolkit/tdd-guide"><img src="https://agentmods.dev/badge/rules/ulises-jeremias/agent-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/rules/ulises-jeremias/agent-toolkit/tdd-guide"><img src="https://agentmods.dev/badge/rules/ulises-jeremias/agent-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.01240 | $0.01240 |
| Opus 5.5 | $0.00496 | $0.00496 |
| Sonnet 5.5 | $0.00248 | $0.00248 |
| Haiku 4.5 | $0.00124 | $0.00124 |
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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: tdd-guide description: Test-Driven Development specialist — enforces red-green-refactor with AAA, test doubles and behavior-first coverage. Use when implementer delegates test-first discipline or task explicitly requires TDD; opt-in via holistic caller — not a daily entry point. tools: Read, Grep, Glob, Bash kind: specialist
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.
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 · 103 lines · 1,240 tokens per session scan A 66eb522a2a23
tdd-guide is a cursor rule published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed today), licensed MIT. It adds 1,240 tokens to every session, about $0.0050 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 cursor rules, from other repositories
always-on
Spec-driven Spring Boot 4 — global guardrails that compensate for Windsurf's lack of a pre-tool-use hook.
production-code
Production code rule — TDD precondition + Spring Boot 4 conventions.
exploratory-charter
Write, run, and debrief exploratory testing charters against Katalon True Platform/TestOps when there is no script to follow. Use when you need to turn a vague area into a charter (mission, areas, oracles, timebox), run a timeboxed unscripted session, log what you find as session notes, judge which findings are real…
test-estimation
Estimate testing effort, duration, and resourcing for a Katalon True Platform/TestOps cycle. Use when the question is how long testing will take, how many testers it needs, whether the scope fits the sprint window, or what a scope change costs in person-hours. Sizes design, manual execution, automated execution and…
incremental-verify
Verify each behavior before building the next. One test, one implementation, one commit. No bulk-writing tests for behavior that does not yet exist.
upload-report
Run automation and upload or verify Katalon Platform reports for Katalon Studio/KRE, JUnit XML, and Playwright reports. Use when you need to combine Katalon MCP project/result discovery with Katalon CLI execution, Katalon Report Uploader, or @katalon/playwright-reporter; configure report folders, report types…