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/validated)<a href="https://agentmods.dev/commands/shashankreddy509/claude-tdd-kit/validated"><img src="https://agentmods.dev/badge/commands/shashankreddy509/claude-tdd-kit/validated/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/validated"><img src="https://agentmods.dev/badge/commands/shashankreddy509/claude-tdd-kit/validated.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.01095 |
| Opus 5.5 | $0.00000 | $0.00438 |
| Sonnet 5.5 | $0.00000 | $0.00219 |
| Haiku 4.5 | $0.00000 | $0.00110 |
Grade A, and why
validated 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 13d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manual-validation sign-off: record what you verified, then move the ticket from its verification column to Done.
This is Stage 5, the last of the gated pipeline (Build → Implement → Ship → Merged →
Validated). Run it after /tdd-pipeline:merged parked the ticket in a verification
column and you actually validated the change on a real build.
Triggers: /tdd-pipeline:validated <KEY> [note], e.g.
/tdd-pipeline:validated PROJ-12 verified on device, rate limiter holds under load.
This is the ONLY command in the pipeline that moves a ticket to Done. That's the point:
Done should mean validated, not merely merged. merged deliberately stops short.
Step 0 — Resolve context
<KEY>from the argument, else the newesttasks/plans/*_plan.md, else the branch name. With no key, stop and ask — this command is entirely about the ticket.- Resolve the Jira MCP dialect ONCE — see
${CLAUDE_PLUGIN_ROOT}/references/jira-mcp.md. It returns the tool names for this machine and whethercloudIdis a parameter (and if so, where to read it from). No Atlassian MCP resolved → STOP and say so: this command is entirely about the ticket, so there is nothing it can do without Jira.
Step 1 — Gate on the current status
Read <KEY>'s status with the resolved get issue tool (request the status field).
- Status is a verification column (the board's column between In Review and Done, e.g. QA, Testing, UAT, Staging; unsure which → ask the user) → proceed.
- Status is already Done → say so and stop. Nothing to do.
- Status is anything earlier (To Do, In Progress, In Review) → stop. The work hasn't
been merged and parked yet; point the user at
/tdd-pipeline:mergedfirst. Closing a ticket that never reached verification is exactly what this gate exists to prevent.
If the board has no verification column at all, merged already moved the ticket to Done
and this command has no role — say so and stop.
Step 2 — Capture the validation note
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.
- 13d ago Changed 3ec955f0564f
- 1mo ago First seen · 113 lines · 0 tokens per session scan A c9345ef1179f
validated 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 1,095 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.
delegate-backlog
Delegate an approved backlog to GitHub Copilot coding agent (async, parallel), then review the resulting PRs with the kit. Trades the in-session gates for throughput; nothing auto-merges. Usage - /delegate-backlog.
search
Search Jira issues using JQL.