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/KevinZai/commanderWrote 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/commands/kevinzai/commander/ccc-tdd)<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-tdd"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-tdd/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/commands/kevinzai/commander/ccc-tdd"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-tdd.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.00057 | $0.01295 |
| Opus 5.5 | $0.00023 | $0.00518 |
| Sonnet 5.5 | $0.00011 | $0.00259 |
| Haiku 4.5 | $0.00006 | $0.00129 |
Grade A, and why
ccc-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 9d 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.
This is a copy
94% identical to tdd — 359 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ccc-tdd — red, green, refactor, prove
CC Commander · /ccc-tdd · drives one feature or bug fix through the TDD cycle and reports real test and coverage output.
When to use / when not to
Use for new features, new functions or components, bug fixes (reproduce the bug in a test first), refactors of existing code, and critical business logic.
Do not use for full user-flow tests (use /ccc-e2e) or for raising coverage on code that already exists (use /ccc-test-coverage).
Arguments
$ARGUMENTS is the feature or bug to build, for example /ccc-tdd a function that scores market liquidity from volume, spread and trader count. If it is empty, ask what to build.
Delegation
When the tdd-guide agent is installed (bundled with the ECC vendor pack at agents/tdd-guide.md, with the tdd-workflow skill at skills/tdd-workflow/SKILL.md), delegate the cycle to it with the Agent tool and pass the steps below as its contract. When it is not installed, run the steps in this session. The user's selected model is preserved; do not override it.
What happens
-
Detect the test runner and coverage command. Read
package.jsonscripts and config files and pick the first match:Indicator Test command Coverage command vitest.config.*npx vitest run <file>npx vitest run --coveragejest.config.*or ajestkey inpackage.jsonnpx jest <file>npx jest --coveragepytest.ini/pyproject.tomlwith pytestpytest <file>pytest --cov=<pkg> --cov-report=term-missinggo.modgo test ./<pkg>/...go test -cover ./...Cargo.tomlcargo test <name>cargo llvm-covpackage.jsontestscript onlynpm test -- <file>npm test -- --coverageRead the coverage threshold from the project config (
coverageThreshold,--cov-fail-under, CI config). Use 80% only when the project sets none. If no runner is found, ask the user for the test command.
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.
- 9d ago Changed · -245 lines · +29 tokens per session c2a6c4e3f797
- 1mo ago First seen · 329 lines · 28 tokens per session scan A 2c01020e1112
ccc-tdd is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 1,295 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to tdd, differing in 359 lines, and is treated as a copy.
Other commands, from other repositories
loop
Autonomous execution loop. Runs the TDD cycle repeatedly until all tasks in an epic are complete, with circuit breaker protection and PR workflow.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
symfony-tdd-pest
Start a TDD workflow using Pest PHP for Symfony with RED-GREEN-REFACTOR cycle.
debug
Systematic root-cause investigation, then fix with TDD — never proposes a fix before finding the cause; resumable diagnosis + regression test in .orc/ state. Workspace-aware. For a quick one-off look without session state, prefer the bundled /debug.
dev-tdd
Implements a feature by following the TDD (Test-Driven Development) cycle.
work-flow-feature
Complete workflow for developing a new feature, from exploration to merge.