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/shashankreddy509/claude-tdd-kitWrote 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/merged)<a href="https://agentmods.dev/commands/shashankreddy509/claude-tdd-kit/merged"><img src="https://agentmods.dev/badge/commands/shashankreddy509/claude-tdd-kit/merged/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/merged"><img src="https://agentmods.dev/badge/commands/shashankreddy509/claude-tdd-kit/merged.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.02057 |
| Opus 5 | $0.00000 | $0.01028 |
| Sonnet 5 | $0.00000 | $0.00411 |
| Haiku 4.5 | $0.00000 | $0.00206 |
Grade A, and why
merged 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-merge cleanup: confirm the PR actually merged, move the Jira ticket to the project's post-review state, sync the default branch, and delete the merged feature branch.
This is Stage 4 of the gated pipeline (Build → Implement → Ship → Merged → Validated).
Run it after you've reviewed and merged the PR that /tdd-pipeline:ship opened.
Triggers: /tdd-pipeline:merged [<KEY>|<PR#>], e.g. /tdd-pipeline:merged PROJ-12.
Argument (optional): the ticket key or PR number. If omitted, derive from the most recently
modified tasks/plans/*_plan.md, or from the current branch (feat/PROJ-12-slug → PROJ-12).
Never merges — it runs after a merge you performed, and refuses if the PR isn't merged. Never deploys — deploy paths are project-specific (tags, pipelines, hosts). Never moves a ticket to Done when the board has a verification column — see Step 2.
Step 0 — Resolve context
- Determine
<KEY>from the argument, the newest plan file, or the branch name. With no key, the git cleanup still runs and every Jira step is skipped. - Resolve the Jira MCP dialect ONCE — see
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 → log the skip line from that file, run the git cleanup, and skip every Jira step below. - Determine the default branch — do NOT assume
main:git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's|^origin/||' \ || gh repo view --json defaultBranchRef --jq .defaultBranchRef.name
Step 1 — Verify the merge actually happened
Don't trust the caller, and don't treat "closed" as "merged" — a closed-unmerged PR must never close a ticket or delete a branch.
gh pr view <#|branch> --json number,url,state,mergedAt,mergeCommit,headRefName
Falling back to a search when only a key is known:
gh pr list --search "<KEY>" --state merged --json number,url,mergedAt,mergeCommit,headRefName --limit 5
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 · 166 lines · 0 tokens per session scan A 4c1790e92e09
merged is a command published in the GitHub repository shashankreddy509/claude-tdd-kit (2 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,057 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
commit-push-pr
An automated Git workflow that checks a project, synchronizes documentation, commits changes, and can create or merge a GitHub pull request. A pull request is a request for teammates to review and add changes to a shared codebase.
auto
An automated coding workflow runs a software task from planning through code changes, checks, and a pull request. A pull request is a proposed change for review before it is merged into the main codebase.
sync
A command that pulls the latest code from the main Git branch and updates the project's key planning and instruction documents to match it.
pull
A quick command that downloads the latest commits from the main Git branch into the current project.
worktree-cleanup
A command for removing a Git worktree, which is a separate working folder linked to the same repository, after its pull request is merged.
quick-commit
A quick Git command for committing and pushing a small code change. Git is the tool that records code versions and sends them to a shared repository.