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/luisabwk/krakenWrote 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/luisabwk/kraken/tdd-coach)<a href="https://agentmods.dev/agents/luisabwk/kraken/tdd-coach"><img src="https://agentmods.dev/badge/agents/luisabwk/kraken/tdd-coach/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/agents/luisabwk/kraken/tdd-coach"><img src="https://agentmods.dev/badge/agents/luisabwk/kraken/tdd-coach.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.00046 | $0.00379 |
| Opus 5.5 | $0.00018 | $0.00152 |
| Sonnet 5.5 | $0.00009 | $0.00076 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
tdd-coach 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 58 lines · 46 tokens per session scan A 8e9fd8f7fb3f
tdd-coach is an agent published in the GitHub repository luisabwk/kraken (2 stars, last pushed 7mo ago), with no licence file. It adds 46 tokens to every session and 379 once invoked, about $0.0002 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-31.
Other agents, from other repositories
verifier
Verification and QA specialist. Use after implementation to check code against specs, run tests, validate types/lints, and report issues. Reports problems — does not fix them.
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
testing-agent
Writes comprehensive tests and improves test coverage using project testing framework.
verifier
Validates completed work. Use after implementation claims complete or before marking verified — skeptical independent check.
fixer
A coding agent that fixes reported bugs using test-driven development, or TDD: reproduce the problem, write a failing test, change the code, and confirm the tests pass. It first checks what the affected feature is meant to do.
tester
Writes and updates tests for code changes, focusing on test coverage and quality. Use for parallel test writing while main agent implements features.