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 skills/luisalima/agent-policy-kit/tddnpx skills add luisalima/agent-policy-kit --skill tddgit clone --depth 1 https://github.com/luisalima/agent-policy-kitWrote 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/skills/luisalima/agent-policy-kit/tdd)<a href="https://agentmods.dev/skills/luisalima/agent-policy-kit/tdd"><img src="https://agentmods.dev/badge/skills/luisalima/agent-policy-kit/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.00032 | $0.00229 |
| Opus 5 | $0.00016 | $0.00114 |
| Sonnet 5 | $0.00006 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
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 Discipline
Walk the TDD cycle for the current task:
- Identify the behavior to assert. If unclear, ask before proceeding.
- Write the failing test first. Show what it asserts and why.
- Run the suite. Confirm the new test fails for the right reason, not a typo or import error. If it passes immediately, stop and reassess the test.
- Write the minimum source change to make it pass. No extras.
- Run the suite again. Confirm green.
- Keep the change focused.
Spike Exception
If the behavior is unknown, such as UI layout, an unfamiliar API, or prompt engineering:
- Declare the spike up front:
Spike to learn X; I will discard and TDD after. - Isolate it from the production change.
- Show the discard before the real implementation lands.
An undeclared deviation is skipped tests, not a spike.
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 · 26 lines · 32 tokens per session scan A 88abaeb1f6e5
tdd is a skill published in the GitHub repository luisalima/agent-policy-kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 229 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-08-31.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.