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 rules/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/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.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.01240 | $0.01240 |
| Opus 5 | $0.00620 | $0.00620 |
| Sonnet 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 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.
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.
- 4d 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 (16 stars, last pushed 5d ago), licensed MIT. It adds 1,240 tokens to every session, about $0.0062 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 cursor rules, from other repositories
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…
solana-transaction-safety
Safe Solana transaction submission patterns using Helius Sender.
execute-test
Execute Katalon True Platform/TestOps tests when the input is an existing test case, manual test case list, test suite, suite collection, execution request, or "run with AI" instruction. Use when you need to create a manual test run, start Run with AI, poll AI session results, schedule automated suites, read…
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…
test-review
Review Katalon True Platform/TestOps test quality and coverage before tests enter the delivery pipeline. Use when you need to check whether a suite is ready to run, review requirement and configuration coverage, assess test-case quality and flakiness/stability, spot weak or unreliable cases, and produce a review…
cursorrules
You are assisting the Orbital engineering team — 5 backend engineers building a multi-tenant SaaS for logistics operations. TypeScript monorepo using NestJS, PostgreSQL (drizzle-orm), and BullMQ. All engineers use shared conventions.