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.
npx agentmods add skills/kelp/agent-plugins/tdd-initnpx skills add kelp/agent-plugins --skill tdd-initgit clone --depth 1 https://github.com/kelp/agent-pluginsWhat 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 | $0.00030 | $0.00345 |
| Opus 5 | $0.00015 | $0.00172 |
| Sonnet 5 | $0.00006 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
tdd-init 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 2d 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
/tdd-init
Add TDD pipeline configuration to this project's CLAUDE.md.
Procedure
1. Read the configuration fragment
Read the file at
${CLAUDE_PLUGIN_ROOT}/docs/claude-md-fragment.md.
This contains the TDD pipeline configuration template
formatted as a CLAUDE.md section.
2. Check current CLAUDE.md
- If no
CLAUDE.mdexists in the project root, create one with just a# CLAUDE.mdheader followed by the fragment content. - If
CLAUDE.mdexists, check if it already contains "TDD Pipeline Configuration". If so, report "TDD pipeline configuration already present" and stop. - If
CLAUDE.mdexists but lacks the configuration, append the fragment content to the end of the file.
3. Report result
Tell the user what you did:
- "Created CLAUDE.md with TDD pipeline configuration"
- "Added TDD pipeline configuration to existing CLAUDE.md"
- "TDD pipeline configuration already present in CLAUDE.md"
4. Next steps
Tell the user to fill in the template values:
- Test command for individual modules
- Source and test file path patterns
- Build integration steps
- Full test and lint commands
- Any language-specific agent context
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.
- 2d ago First seen · 52 lines · 30 tokens per session scan A a88120629d7e
tdd-init is a skill published in the GitHub repository kelp/agent-plugins (2 stars, last pushed 9d ago), licensed MIT. It adds 30 tokens to every session and 345 once invoked, about $0.0002 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 skills, from other repositories
test
Generate tests and coverage plans. Triggers: "test", "generate tests and coverage plans.", "test skill".
auto-loop
TDD-based autonomous development loop with checkpoint recovery and observability changelog.
test-first
Drive one feature through a strict TDD Red-Green-Refactor cycle with checklists for each phase. Use when implementing new functionality test-first, or when the user runs /test-first.
feature
End-to-end feature workflow around the agent — spec by interview, a plan of 2–5-minute tasks, test-first execution with checkpoint commits, then an evidence-gated finish. Effort-scaled: a one-sentence diff skips straight to implementation; a real feature gets spec.md → plan.md → task-by-task TDD, with all state in…
testing-go
Writes tests following TDD (using go test, testify, and rapid) best practices. Use when writing unit tests, integration tests, or table-driven tests in Go.
agent-integration
Run all three agent integration phases sequentially: research, write-tests, and implement using E2E-first TDD (unit tests written last). For individual phases, use /agent-integration:research, /agent-integration:write-tests, or /agent-integration:implement. Use when the user says "integrate agent", "add agent…