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/hculap/better-codeWrote 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/hculap/better-code/tdd-dev)<a href="https://agentmods.dev/plugins/hculap/better-code/tdd-dev"><img src="https://agentmods.dev/badge/plugins/hculap/better-code/tdd-dev/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/hculap/better-code/tdd-dev"><img src="https://agentmods.dev/badge/plugins/hculap/better-code/tdd-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tdd-dev 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 6d 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-dev",
"version": "0.2.2",
"description": "Transform Claude Code into a strict TDD practitioner that enforces Red→Green→Refactor cycles",
"author": {
"name": "Szymon Paluch"
},
"repository": "https://github.com/hculap/better-code",
"homepage": "https://github.com/hculap/better-code#readme",
"license": "MIT",
"keywords": ["tdd", "test-driven-development", "testing", "red-green-refactor", "quality"],
"agents": [
"./agents/tdd-developer.md"
]
}
What it installs
The manifest is a name and a version. 1 skill, 5 commands, 1 agent, 3 hooks travel with it, and installing the plugin installs all of them — 760 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill TDD Methodology A 85 tokens
- Command tdd-bug A 7 tokens
- Command tdd-feature A 9 tokens
- Command tdd-refactor A 7 tokens
- Command tdd-start A 8 tokens
- Command tdd-stop A 8 tokens
- Agent tdd-developer A 636 tokens
- Hook PostToolUse A not measured
- Hook PreToolUse A not measured
- Hook UserPromptSubmit A not measured
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.
- 6d ago Changed c9617c20439d
- 1mo ago First seen · 16 lines scan A 8f1e0c6fa25e
tdd-dev is a plugin published in the GitHub repository hculap/better-code (2 stars, last pushed 7d 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
implementation
Disciplined implementation stage: execute approved plans inline (/implementation:implement) or via orchestrated worker subagents (/implementation:implement-dispatch) with incremental validation, TDD-by-default cadence, green-checkpoint commits, scope-fence drift detection, and divergence detection that routes back.
mutation-testing
Measures whether a test suite can actually detect faults, not merely execute code: /mutation-testing:principles answers operator, mutant-state, and metric questions from the primary literature; /mutation-testing:setup verifies the ecosystem's mutation tool and writes the tracked config; /mutation-testing:audit ru.
debugging
Debug observed failures via a disciplined six-phase loop: build a fast deterministic reproduction signal, reproduce, rank falsifiable hypotheses, instrument, fix with a regression test, then clean up and post-mortem.
tdd-guard
Automated Test-Driven Development enforcement.
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…
ring-default
Core skills library from the Lerian Team: TDD, code review, collaboration patterns, and proven techniques. 23 essential skills for software engineering excellence, including plan authoring and execution.