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/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/plugins/shashankreddy509/claude-tdd-kit/tdd-pipeline"><img src="https://agentmods.dev/badge/plugins/shashankreddy509/claude-tdd-kit/tdd-pipeline.svg" alt="Reviewed on agentmods" width="80" 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 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.
What it actually says
{
"name": "tdd-pipeline",
"version": "1.17.5",
"description": "Gated TDD build pipeline: /build plans a feature or bug fix and waits for click-approval; /implement resolves the test command for any stack, runs the build-coordinator through test-writer \u2192 verify-red \u2192 implementer \u2192 test-runner/implementer fix loop \u2192 adversarially-verified code review (Critical and Must-fix findings hard-stop, post-review edits must re-pass review), then auto-runs /ship, which gates the commit on a verification receipt, then opens the PR and moves the ticket to In Review. 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. 7 commands, 13 agents travel with it, and installing the plugin installs all of them — 864 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 build-epic 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 136 tokens
- Agent code-review-coordinator A 85 tokens
- Agent implementer A 71 tokens
- Agent code-quality-reviewer A 54 tokens
- Agent money-logic-reviewer A 103 tokens
- Agent test-writer A 27 tokens
- Agent changelog A 62 tokens
- Agent kotlin-best-practices A 58 tokens
- Agent memory-analyzer A 36 tokens
- Agent test-runner A 67 tokens
- Agent concurrency-reviewer A 80 tokens
- Agent security-reviewer A 41 tokens
- Agent planner A 44 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.
- 5d ago Changed f6af5bc0157a
- 9d ago Changed b8ec7193a58d
- 10d ago Changed 9957b0d529ad
- 11d ago Changed d7c02430f944
- 13d ago Changed c0fe1e0d18d1
- 16d ago Changed a65a4595cfe8
- 18d ago Changed 108e48a26d02
- 21d ago Changed 42195e715b70
- 25d ago Changed f3f6ac17fdbe
- 28d ago First seen · 17 lines scan A 05fa61d453ad
tdd-pipeline is a plugin published in the GitHub repository shashankreddy509/claude-tdd-kit (2 stars, last pushed 5d 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
knowledge-virtuoso
18 knowledge skills: design patterns, refactoring, SOLID, debugging, clean architecture, testing, API design, security, agent security, context engineering, docs lookup, scrum, performance, microservices, CI/CD, accessibility, database design, and motion design.
jira-pack
Issue-tracker pack: /jira-fix takes a ticket link of any type, verifies tracker access, classifies it as a defect or a change, reproduces the defect or writes a failing acceptance test for the change, routes the work to core executors, comments back with evidence and moves the ticket to the QA column. Opt-in; requires.
whetstone
Engineering-craft skills: red-green TDD, flaky-test audit, diagnosis, doubt review, grilling, merge-conflict resolution, research reports with grounded claims, HTML reports, skill linting and a column budget. Every gate among them carries a deterministic self-verify.
es6kr
Core fundamental skills: brief, fa, tdd, and web-browser.
superpowers-deepseek-v4
Superpowers DeepSeek v4: composable agent skills for TDD, debugging, and collaboration. Independently maintained; not identical to obra/superpowers.
safeword
AI coding agent workflows: BDD, auto-linting, quality reviews, debugging, and refactoring. Run safeword install in a project to enroll it.