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/MadeByTokens/claude-code-plugins-madebytokensWrote 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/madebytokens/claude-code-plugins-madebytokens/tdd-status)<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.
<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>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.00006 | $0.00862 |
| Opus 5 | $0.00003 | $0.00431 |
| Sonnet 5 | $0.00001 | $0.00172 |
| Haiku 4.5 | $0.00001 | $0.00086 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- tdd-status — 100% identical, 0 lines differ
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:
STOP.📊 **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"
Step 2: Parse State Information
Extract from the state file:
active- whether loop is runningiteration- current iteration numbermaxIterations- maximum allowed iterationsphase- current phase (WRITING_TESTS/WRITING_CODE/REVIEWING)testFilePaths- array of test file pathsimplFilePaths- array of implementation file pathslastVerdict- most recent verdict (WEAK_TESTS/WEAK_CODE/ALL_PASS)lastFeedback- feedback objectmutationScore- mutation testing score (if available)mutationSurvivors- array of surviving mutants (if available)startedAt- when loop startedcompletedAt- 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
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
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 First seen · 125 lines · 6 tokens per session scan A 5df21ac7c44d
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.
Other commands, from other repositories
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.
hub-tdd
TDD workflow for MCP Hub implementation. Types → Tests (red) → Implementation (green) with git gates.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.