tdd-status

tdd-status is a command for Claude Code from MadeByTokens/claude-code-plugins-madebytokens. It costs 6 tokens per session (862 once invoked), scanned A, original, MIT.

A command that displays the current state of a test-driven development (TDD) loop. TDD means writing tests, implementing code, and reviewing the results in repeated cycles.

In plain words
What is it for?
Use it to view the iteration, test and implementation files, latest verdict, feedback, mutation-testing results, and stop or completion details.
Why use it?
It shows whether a TDD loop is active, which phase it is in, and what happened in the latest cycle without inspecting its state file manually.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the bon-cop-bad-cop plugin — 4 commands, 3 agents shipped together

Good fit Use it to view the iteration, test and implementation files, latest verdict, feedback, mutation-testing results, and stop or completion details.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/madebytokens/claude-code-plugins-madebytokens/tdd-status
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.

Clone the repo
git clone --depth 1 https://github.com/MadeByTokens/claude-code-plugins-madebytokens

Made for: Claude Code.

Or install bon-cop-bad-cop, the plugin that ships this one along with the rest of its 4 commands, 3 agents.

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

agentmods badge for tdd-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/madebytokens/claude-code-plugins-madebytokens/tdd-status/github.svg)](https://agentmods.dev/commands/madebytokens/claude-code-plugins-madebytokens/tdd-status)
Your own site
<a href="https://agentmods.dev/commands/madebytokens/claude-code-plugins-madebytokens/tdd-status"><img src="https://agentmods.dev/badge/commands/madebytokens/claude-code-plugins-madebytokens/tdd-status/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.

agentmods 80×15 button for tdd-status

Your own site · 80×15
<a href="https://agentmods.dev/commands/madebytokens/claude-code-plugins-madebytokens/tdd-status"><img src="https://agentmods.dev/badge/commands/madebytokens/claude-code-plugins-madebytokens/tdd-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 862 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00006 $0.00862
Opus 5 $0.00003 $0.00431
Sonnet 5 $0.00001 $0.00172
Haiku 4.5 $0.00001 $0.00086

Measured 9d ago against content hash 5df21ac7c44d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

tdd-status 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/bon-cop-bad-cop/commands/tdd-status.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/tdd-status Command

When the user runs /tdd-status, follow these instructions:

Step 1: Read State File

Try to read .tdd-working/state.json:

  • If file doesn't exist: Display:
    📊 **TDD Loop Status**
    
    Status: No active loop
    
    No .tdd-working/state.json found in current directory.
    
    To start a new loop: /tdd-loop "Your requirement here"
    
    STOP.

Step 2: Parse State Information

Extract from the state file:

  • active - whether loop is running
  • iteration - current iteration number
  • maxIterations - maximum allowed iterations
  • phase - current phase (WRITING_TESTS/WRITING_CODE/REVIEWING)
  • testFilePaths - array of test file paths
  • implFilePaths - array of implementation file paths
  • lastVerdict - most recent verdict (WEAK_TESTS/WEAK_CODE/ALL_PASS)
  • lastFeedback - feedback object
  • mutationScore - mutation testing score (if available)
  • mutationSurvivors - array of surviving mutants (if available)
  • startedAt - when loop started
  • completedAt - when loop ended (if completed)
  • stoppedReason - why loop stopped (if stopped)

Step 3: Display Status

Format and display the status report:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📊 **TDD Loop Status**
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Status: <if active: "🟢 Active" else: "🔴 Inactive (<stoppedReason>)">
Iteration: <iteration> / <maxIterations>
Current Phase: <phase>

Requirement: (see .tdd-working/inputs/requirement.md)

Files Generated:
  Tests (<number of testFilePaths>):
    <list each test file path with "  - " prefix>

  Implementation (<number of implFilePaths>):
    <list each impl file path with "  - " prefix>

Last Verdict: <lastVerdict or "None yet">

<if mutationScore exists:>
Mutation Score: <mutationScore * 100 rounded to 1 decimal>%
<end if>

<if mutationSurvivors exists and has items:>
Mutation Survivors: <count>
  <list first 3 survivors: "  - Line <line>: <mutation>">
  <if more than 3: "  ... and <count - 3> more">
<end if>

<if lastFeedback.test_writer or lastFeedback.code_writer:>
Last Feedback:
  <if lastFeedback.test_writer: "  To Test Writer: <first 80 chars>...">
  <if lastFeedback.code_writer: "  To Code Writer: <first 80 chars>...">
<end if>

Duration: <calculate time from startedAt to (completedAt or now)>
Working directory: .tdd-working/
State file: .tdd-working/state.json

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Read the full file on GitHub · 125 lines

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. 9d ago First seen · 125 lines · 6 tokens per session scan A 5df21ac7c44d

Subscribe to this mod's changes

tdd-status is a command published in the GitHub repository MadeByTokens/claude-code-plugins-madebytokens (2 stars, last pushed 7mo ago), licensed MIT. It adds 6 tokens to every session and 862 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.