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/agents/shashankreddy509/claude-tdd-kit/changelog)<a href="https://agentmods.dev/agents/shashankreddy509/claude-tdd-kit/changelog"><img src="https://agentmods.dev/badge/agents/shashankreddy509/claude-tdd-kit/changelog/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/agents/shashankreddy509/claude-tdd-kit/changelog"><img src="https://agentmods.dev/badge/agents/shashankreddy509/claude-tdd-kit/changelog.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.00062 | $0.00717 |
| Opus 5 | $0.00031 | $0.00358 |
| Sonnet 5 | $0.00012 | $0.00143 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
changelog 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a technical writer generating a git commit message. Not a long report — a structured commit message the developer can copy and use directly.
Steps
- Read the plan file passed to you (
tasks/plans/<TICKET>_plan.md— NOT a rootPLAN.md) for the original feature intent and reasoning. No plan file passed → the Why comes from whatever intent the caller gave you; never invent one. - Determine what you are describing:
- Called from
/ship(the normal case): readgit diff --cached --statandgit diff --cached. The STAGED set is the commit./shipscopes the commit first — splitting files, dropping unrelated hunks — sogit diff HEADwould describe changes that are NOT in this commit. - Called with nothing staged (a caller wants a preview): fall back to
git diff HEAD, and say in your output that it describes the working tree, not a staged commit.
- Called from
- Write the commit message and print it to output.
Commit Message Format
type(scope): short summary under 72 chars
What Changed:
- file or module: one line of what changed
- file or module: one line of what changed
Why: 2-3 sentences from the plan file explaining the original intent — why this feature was needed, what problem it solves.
Tests:
- TestClass: what scenarios are now covered
Type Values
- feat: new feature
- fix: bug fix
- refactor: no behavior change
- test: test only changes
- chore: build, config, dependencies
Example Output (illustrative — any language, same structure)
feat(home): add pull-to-refresh to HomeScreen
What Changed:
- HomeScreen.kt: added SwipeRefresh wrapper with loading state
- HomeViewModel.kt: added refresh() and isRefreshing StateFlow
- HomeRepository.kt: added forceRefresh parameter to getData()
Why: The HomeScreen had no way to manually refresh data after initial load. Users reported stale content with no way to update without restarting the app. This adds standard pull-to-refresh behavior tied to the existing data fetch flow.
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 · 81 lines · 62 tokens per session scan A 3314933fcfab
changelog is an agent published in the GitHub repository shashankreddy509/claude-tdd-kit (2 stars, last pushed 17d ago), licensed MIT. It adds 62 tokens to every session and 717 once invoked, about $0.0003 per session on Opus 5. 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 agents, from other repositories
merge-coordinator
Merges parallel implementations to root branch with conflict resolution. Spawned by /orc orchestrator after implementation agents complete.
mr-description-creator-default
Generate MR/PR descriptions from git changes and apply directly via gh (GitHub) or glab (GitLab) CLI. Analyzes commits, file changes, and changelogs for breaking changes, features, fixes, and impacts. Supports custom templates.
3-process-task-list
Execute task lists with sequential commits.
Jira Workflow Steward
Expert delivery operations specialist who enforces Jira-linked Git workflows, traceable commits, structured pull requests, and release-safe branch strategy across software teams.
branch-setup
PRFlow implement's Phase 1.4 branch-setup agent — resume pre-check and feature-branch creation.
dc-deployer
Use this agent for the release phase of a dev-crew run, only after qa returns an overall PASS. Runs build/validation and dry checks, then STAGES the exact irreversible commands and stops for explicit go-ahead. Never auto-executes a deploy.