tdd-stop

A command that turns off TDD Dev Mode for the current session. TDD, or test-driven development, means writing a failing test before the code that makes it pass.

In plain words
What is it for?
Use it to resume a normal coding workflow while keeping the TDD commands and methodology available for manual use.
Why use it?
It stops the automatic checks that enforce the test-first workflow when that enforcement is no longer wanted.

Command

Install

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.

agentmods
npx agentmods add commands/hculap/better-code/tdd-stop
Clone the repo
git clone --depth 1 https://github.com/hculap/better-code
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 186 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.00186
Opus 5 $0.00004 $0.00093
Sonnet 5 $0.00002 $0.00037
Haiku 4.5 $0.00001 $0.00019

Measured yesterday against content hash 306353f83138, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

plugins/tdd-dev/commands/tdd-stop.md · 33 lines

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

  1. Remove the flag file: Delete .claude/.tdd-mode-active if it exists

  2. 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:refactor commands explicitly
  • Only automatic hook enforcement is disabled

Confirm TDD mode deactivation.

Changes

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.

  1. yesterday First seen · 33 lines · 8 tokens per session scan A 306353f83138

Subscribe to this mod's changes

tdd-stop is a command published in the GitHub repository hculap/better-code (2 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 186 once invoked, about $0.0000 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.