agentmods.dev

implement

implement is a command for Claude Code from shashankreddy509/claude-tdd-kit. It costs 0 tokens per session (1,148 once invoked), scanned A, original, MIT.

A command that starts a build coordinator to carry out an approved software plan using TDD, or test-driven development: writing tests as part of the implementation process.

In plain words
What is it for?
Use it to execute the most recent approved plan, or a plan for a specified ticket, through the project's full TDD workflow.
Why use it?
It prevents coding from starting without a saved plan that has passed the required approval check.

Command for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: mentions CLAUDE.md; names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the tdd-pipeline plugin — 7 commands, 13 agents shipped together

not rated 2repo changed 9d ago A scan 0 tokens original MIT

Good fit Use it to execute the most recent approved plan, or a plan for a specified ticket, through the project's full TDD workflow.

Compare 6 commands from other repositories ↓
View source ↗ shashankreddy509/claude-tdd-kit
Install

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.

Claude Code
/plugin marketplace add shashankreddy509/claude-tdd-kit
Claude Code
/plugin install tdd-pipeline

Made for: Claude Code.

Or install tdd-pipeline, the plugin that ships this one along with the rest of its 7 commands, 13 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 implement

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/shashankreddy509/claude-tdd-kit/implement"><img src="https://agentmods.dev/badge/commands/shashankreddy509/claude-tdd-kit/implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,148 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.00000 $0.01148
Opus 5.5 $0.00000 $0.00459
Sonnet 5.5 $0.00000 $0.00230
Haiku 4.5 $0.00000 $0.00115

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

Security

Grade A, and why

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

tdd-pipeline/commands/implement.md · 67 lines

How it starts

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

Spawn the build-coordinator agent to execute the full TDD pipeline against an approved plan.

Plan path: $ARGUMENTS

Precondition: an approved plan file must exist at tasks/plans/<TICKET>_plan.md.

  • If a path is given in $ARGUMENTS, use it.
  • If none is given, default to the most recently modified tasks/plans/*_plan.md.
  • If no such file exists → STOP and tell the user to run this plugin's build command first and approve a plan.
  • State which plan file you resolved; if the user named a ticket and the resolved file doesn't match it, STOP and ask.

Approval gate (optional hook — only if $PLAN_GATE_CMD is set; otherwise skip silently)

A plan FILE is not an approval. Read the command once with printenv PLAN_GATE_CMD; call its output <gate> and type it out as a literal line, never through eval (worktree isolation refuses an evaled command). Run <gate> check <resolved-plan-path> (prints approve/revise/discard/unanswered for this exact file version): approve → proceed; discard → STOP, never build a discarded plan; revise → STOP until the plan is rewritten; unanswered → ask via AskUserQuestion ("Build this plan?" — Approve / Cancel) and run <gate> record <resolved-plan-path> approve|discard (Cancel → discard and STOP).

Step 0 — Move Jira ticket to "In Progress" (if a ticket is in scope)

Before spawning the build-coordinator, derive the Jira ticket key from the resolved plan file (e.g. <KEY> from tasks/plans/<KEY>_plan.md).

  • If a key is present, resolve the Jira MCP dialect FIRST — see ${CLAUDE_PLUGIN_ROOT}/references/jira-mcp.md. It returns the tool names to use and whether cloudId is a parameter on this machine. No Atlassian MCP resolved → log the skip line from that file and proceed to the build; the pipeline does not depend on Jira.
  • Look up the ticket's available transitions with the resolved list transitions tool.
  • Find the transition whose to.name is exactly "In Progress" (a Jira convention, not a per-project id). If no such transition exists, log a one-line note (": no 'In Progress' transition in this project's workflow — skipping") and proceed. Do not break the pipeline on Jira weirdness.
  • Apply it with the resolved transition tool, passing that id.
  • On a 400, read the error body: "transition not available/valid from the current status" means the ticket is already in or past In Progress — log the no-op and proceed. Any OTHER error (auth, permissions, project misconfig) → log a one-line warning with the error text and proceed. The pipeline must not depend on Jira being available.
  • If no ticket key can be derived from the plan filename, skip this step silently.
  • Log what you did, e.g. "📋 Moved → In Progress" or "📋 already past In Progress, no transition needed".

Read the full file on GitHub · 67 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 Changed · +2 lines c17e018b7c1c
  2. 11d ago Changed · +4 lines 69437af6efc9
  3. 13d ago Changed · -9 lines f150f28ffce4
  4. 16d ago Changed a789830db87f
  5. 25d ago Changed · +9 lines e97ccd3ec850
  6. 28d ago Changed · +3 lines 58360ae833f1
  7. 1mo ago First seen · 58 lines · 0 tokens per session scan A 3dc132916b42

Subscribe to this mod's changes

implement 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,148 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.

Claude CodeTDDTestingai-agentsautomationclaudedeveloper-toolsjira
Related

Other commands, from other repositories

bugfix

Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.

nWave-ai/nWave · 18 tokens

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.

ajhcs/healthcare-agents · 0 tokens

usage-add

PitWay: Accumulate measured planning or qa token usage onto a milestone.

thixpin/pitway · 0 tokens

speckit.tdd.plan

Derive the feature's test list by delegating to zfa tdd plan (deterministic engine); falls back to LLM-guided derivation only when zfa is unavailable.

arrrrny/zuraffa · 37 tokens

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.

cfrs2005/claude-init · 37 tokens

dashboard

Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.

doncheli/don-cheli-sdd · 14 tokens