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/ship)<a href="https://agentmods.dev/commands/shashankreddy509/claude-tdd-kit/ship"><img src="https://agentmods.dev/badge/commands/shashankreddy509/claude-tdd-kit/ship/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/ship"><img src="https://agentmods.dev/badge/commands/shashankreddy509/claude-tdd-kit/ship.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.04975 |
| Opus 5.5 | $0.00000 | $0.01990 |
| Sonnet 5.5 | $0.00000 | $0.00995 |
| Haiku 4.5 | $0.00000 | $0.00498 |
Grade A, and why
ship 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 5d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Encodes the "stage and commit" ritual: verify (receipt gate) → scope → branch → write the commit message from what is actually staged → commit → push → open PR to the default branch → move the Jira issue to In Review. NO merge (merging is the reviewer's call). NO tag (deploys are project-specific and out of scope).
Argument (optional): explicit file paths to include. If omitted, auto-scope to this session's feature files.
Project config — resolve at runtime, never hardcode
Read the project's CLAUDE.md for a line of the form:
Jira: cloudId=<uuid> key=<KEY>
That line is the ONLY source for the project key. No line → the repo has no Jira wiring: skip every Jira step (steps 2 and 8's transition), ship the PR anyway, and say so in the report.
Resolve the Jira MCP dialect and cloudId before any Jira call, exactly as ${CLAUDE_PLUGIN_ROOT}/references/jira-mcp.md says (§ Calling convention). No Atlassian MCP resolved → log the skip line from that file, ship the PR anyway, and report which transition was skipped.
No Jira: line but the user names a key, and the cloudId is still ambiguous → ask; do not pick one.
Derive the browse URL from the resolved site, not a literal host.
Steps
- Read the pipeline receipt — gate the ship on it. Find the ticket key (branch slug, the user's argument, or the Jira issue for this work) and read
tasks/receipts/<TICKET>.json. The pipeline writes it; keys areticket,plan,sha(HEAD at the last stage written — staleness detection),tree(working-tree fingerprint at that stage),red/green(cmd+ the REAL processexit+at),review(critical,must_fix,warnings,unverified,warning_listoffile:line whatstrings,reviewersthe agents that returned), an optionalgatingblock (required,seeded,readback), andstage(red|green|reviewed|complete). A receipt is a record, not a permission slip — never hand-write or edit one to get past this gate.
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.
- 5d ago Changed · +1 lines 9f33ea8c8adb
- 9d ago Changed · +1 lines bdcc2ef88c5e
- 11d ago Changed · +3 lines 5c34f6e872f8
- 13d ago Changed · -4 lines c351dfdb2628
- 16d ago Changed · +1 lines 198f7490bea4
- 18d ago Changed · +2 lines 2445ef90cfa0
- 28d ago Changed · +19 lines 0a2a76dac115
- 1mo ago First seen · 126 lines · 0 tokens per session scan A 9f47733ccbe6
ship 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 4,975 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
flow
Universal workflow entry point. Use /flow for skill-driven GitHub development. Verbs: start, commit, pr, review, address, merge, resolve, release, status, learn, setup, explain, debug, design, brainstorm, issue.
commit-push-pr
Commit, push, and open a PR.
standup
Review my git commits from the past workday and generate a standup summary.
gsd:remove-phase
Remove a future phase from roadmap and renumber subsequent phases.
iterate
Execute a single Ralph loop iteration - complete one work unit from tasks.md with proper commits and progress tracking.
weekly-summary
Generate weekly work summary from git activity.