Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add shashankreddy509/claude-tdd-kit/plugin install tdd-pipelineWrote 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/shashankreddy509/claude-tdd-kit/build)<a href="https://agentmods.dev/commands/shashankreddy509/claude-tdd-kit/build"><img src="https://agentmods.dev/badge/commands/shashankreddy509/claude-tdd-kit/build/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/shashankreddy509/claude-tdd-kit/build"><img src="https://agentmods.dev/badge/commands/shashankreddy509/claude-tdd-kit/build.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.00000 | $0.02259 |
| Opus 5.5 | $0.00000 | $0.00904 |
| Sonnet 5.5 | $0.00000 | $0.00452 |
| Haiku 4.5 | $0.00000 | $0.00226 |
Grade A, and why
build 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.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan a new feature inline, iterate until approved, then auto-hand off to implementation.
This command runs in the MAIN thread (not a subagent) so the plan is shown to you directly in chat and you can iterate on it in real time. No plan file is written until you explicitly approve.
Feature request: $ARGUMENTS
Flow
0. Triage-file check (bug path) — DO THIS FIRST
- Derive the ticket key from
$ARGUMENTS(e.g.<KEY>) if one is present. - If a key is present, check for
tasks/<TICKET>-triage.mdin the open project (a triage artifact from any bug-triage workflow). If it exists, this is a bug fix with a confirmed root cause — do NOT re-explore from scratch:- Read the triage artifact. Trust its stated verdict, root cause, affected files, what it excluded as adjacent, and any fix-plan seed it proposes.
- If the verdict is
not-reproducible/invalid/pre-existing, STOP and tell the user — there is nothing to build; surface the triage recommendation (close it / not our change). - If
real-bug, write a LEAN fix-plan: the smallest correct change at the shared point (not per-caller), the one test from the seed, and the toggle gate if the seed names one. Skip the broad exploration in step 1 — the root cause is already proven. Present it inline (step 2), iterate (step 3), and on approval (step 4) write it as the plan file.
- If no triage file, this is the normal feature/plan path — continue to step 1.
1. Explore (read-only)
- Enter plan mode.
- Read the codebase relevant to the request. You MAY spawn read-only
Exploresubagents in parallel for breadth, or theplannersubagent as a research helper to draft an approach — but those return text to you; they do NOT write any file. - Find code to reuse. Before planning anything new, search the repo for components,
functions and methods that already do part of the job — the same UI shape (a card, a row, a
dialog) or the same data read/write — and that this ticket could call with its own data or
labels. Each one goes in the plan's
## Reuse. A near-copy the plan never named is the duplication the reviewer will block later. - UI ticket? Resolve its mock now. Check the ticket for a mock reference, then the project's
design directory (CLAUDE.md may name it, e.g.
design/exports/). Whatever you find goes in the plan's## Design Reference. A UI ticket with no mock anywhere is worth surfacing — without one the build ships generic sample UI instead of the designed screen.
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 76e1c4e71a8e
- 13d ago Changed · -35 lines 371ee3adb63f
- 16d ago Changed · -30 lines 8dcf1417e724
- 18d ago Changed · +9 lines 214ff0a75906
- 28d ago Changed · +10 lines 22a26324b3d6
- 1mo ago First seen · 179 lines · 0 tokens per session scan A a8a71282ec54
build is a command published in the GitHub repository shashankreddy509/claude-tdd-kit (2 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,259 tokens. 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
create
Command "create" from freema/mcp-jira-stdio, covering /jira:create, usage, examples and what happens.
jira-discover-project
Discover JIRA project context for intelligent defaults and usage patterns.
plan-backlog
Turn an idea, brief, or document into a well-formed backlog and create it in your tracker after approval. Guided by default; --quick for a one-shot draft. Usage - /plan-backlog [--quick].
plan-definition
Turn a spark (an idea, even a one-liner) into a clear product definition through a guided discovery phase, then hand it to plan-backlog. Facilitate, never decide. Usage - /plan-definition.
work-story
Work a user story end to end — fetch the ticket, plan, implement, verify gates, and open the PR. Usage - /work-story PROJ-1234 [--auto-approve].
Agent Mail for real-time coordination between agents.