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/plugins/shashankreddy509/claude-tdd-kit/tdd-pipeline)<a href="https://agentmods.dev/plugins/shashankreddy509/claude-tdd-kit/tdd-pipeline"><img src="https://agentmods.dev/badge/plugins/shashankreddy509/claude-tdd-kit/tdd-pipeline.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
tdd-pipeline 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 8d 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.
What it actually says
{
"name": "tdd-pipeline",
"version": "1.5.5",
"description": "Gated TDD build pipeline: /build plans a feature or bug fix and waits for click-approval; /implement runs the build-coordinator through test-writer \u2192 verify-red \u2192 implementer \u2192 test-runner \u2192 adversarially-verified code review \u2192 changelog (Critical findings hard-stop, post-review edits must re-pass review); /ship gates the commit on a verification receipt, then posts the pipeline summary to Jira and moves the ticket to In Review. Ships an /inline-build skill that runs the same pipeline entirely in the main thread with no subagent spawns. Plans carry a Design Reference so UI tickets are built to their mockup PNG instead of generic sample UI.",
"author": {
"name": "Shashank Reddy Ganta"
},
"keywords": [
"tdd",
"pipeline",
"code-review",
"money-logic",
"concurrency",
"jira"
]
}
What it installs
The manifest is a name and a version. 6 commands, 13 agents travel with it, and installing the plugin installs all of them — 768 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Command ship A 0 tokens
- Command merged A 0 tokens
- Command validated A 0 tokens
- Command build A 0 tokens
- Command implement A 0 tokens
- Command review A 0 tokens
- Agent build-coordinator A 109 tokens
- Agent code-review-coordinator A 85 tokens
- Agent money-logic-reviewer A 103 tokens
- Agent implementer A 34 tokens
- Agent kotlin-best-practices A 54 tokens
- Agent memory-analyzer A 36 tokens
- Agent test-runner A 56 tokens
- Agent changelog A 62 tokens
- Agent concurrency-reviewer A 80 tokens
- Agent planner A 44 tokens
- Agent test-writer A 27 tokens
- Agent code-quality-reviewer A 37 tokens
- Agent security-reviewer A 41 tokens
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.
- 8d ago First seen · 17 lines scan A b8b44a630d3f
tdd-pipeline is a plugin published in the GitHub repository shashankreddy509/claude-tdd-kit (2 stars, last pushed 16d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
superpowers
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques.
ring marketplace
Lerian Studio plugin marketplace: Core software engineering skills (TDD, debugging, code review), specialized developer agents (Backend, DevOps, Frontend, QA, SRE) plus 12 code-review reviewers (9 default hard-gate reviewers and 3 conditional stack specialists), product planning workflows (8-gate pre-dev system), and…
code-quality
Code quality pipeline — SOLID refactoring, TDD workflow, design patterns, performance optimization, and 6 specialist review agents.
pm-dev
Shipping discipline for PMs who code: TDD workflow, pre-commit verification loop, security review, research-before-build.
epic
3 commands + 25 auto-trigger skills + self-evolving agent harness. Less to remember, more automation.
dev-loop
loop-orchestrator's verification loop (TDD / PDCA / Reflexion) with the plan step FIXED to a wiki-grounded planning methodology (wiki-plan): every design decision is routed to a bundled semantic-layer wiki before code is written. Adds a knowledge-capture loop — sessions emit verified insights, and knowledge-flush…