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/hculap/better-codeWrote 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/hculap/better-code/tdd-stop)<a href="https://agentmods.dev/commands/hculap/better-code/tdd-stop"><img src="https://agentmods.dev/badge/commands/hculap/better-code/tdd-stop/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/hculap/better-code/tdd-stop"><img src="https://agentmods.dev/badge/commands/hculap/better-code/tdd-stop.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.00008 | $0.00186 |
| Opus 5.5 | $0.00003 | $0.00074 |
| Sonnet 5.5 | $0.00002 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
tdd-stop 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.
What it actually says
TDD Mode Deactivation
Disable TDD Dev Mode for this session. Hook enforcement will stop and normal coding workflow resumes.
Deactivation Steps
-
Remove the flag file: Delete
.claude/.tdd-mode-activeif it exists -
Confirm deactivation:
TDD Dev Mode: DISABLED
Hook enforcement is now OFF.
Normal coding workflow resumed.
To re-enable: /tdd-dev:start
Note
Even with TDD mode disabled:
- The tdd-methodology skill remains available if you ask about TDD
- You can still use
/tdd-dev:feature,/tdd-dev:bug,/tdd-dev:refactorcommands explicitly - Only automatic hook enforcement is disabled
Confirm TDD mode deactivation.
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 · 33 lines · 8 tokens per session scan A 306353f83138
tdd-stop is a command published in the GitHub repository hculap/better-code (2 stars, last pushed 7d ago), licensed MIT. It adds 8 tokens to every session and 186 once invoked, about $0.0000 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 commands, from other repositories
workflow-implement
Exécuter la phase d'Implémentation - développement sprint avec TDD/BDD.
tdd
Correction de Bug en Mode TDD/BDD.
fix
Correction automatisee des bugs identifies par la QA Recette.
forge
/forge Full Forge pipeline (semi-auto + parallel) /forge [prd-file] Forge a specific PRD /forge --blitz Forge with TDD enforcement.
refactor
You are the Refactor Specialist, a rigorous code quality engineer who improves code structure, maintainability, and performance while preserving behavior. You never break working code - you make it better.
blitz
/blitz is a thin alias for /go --mode=semi-auto --parallel --tdd. It runs the full /go pipeline at maximum speed: semi-auto remediation + parallel wave execution + TDD enforcement. Blitz is for well-defined PRDs with independent stories.