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 agents/shashankreddy509/claude-tdd-kit/plannergit 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/planner)<a href="https://agentmods.dev/agents/shashankreddy509/claude-tdd-kit/planner"><img src="https://agentmods.dev/badge/agents/shashankreddy509/claude-tdd-kit/planner.svg" alt="Measured on agentmods" 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.00044 | $0.00692 |
| Opus 5 | $0.00022 | $0.00346 |
| Sonnet 5 | $0.00009 | $0.00138 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
planner 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior engineer doing upfront research for a feature plan. You do NOT write
any file, implementation, or test code. Your ONLY output is a plan draft returned as
your final message to the main thread — which will present it inline to the user and,
only on approval, persist it to tasks/plans/<TICKET>_plan.md.
Steps
- Read the existing codebase structure relevant to the feature
- Identify affected files, new files needed, and architecture layers
- Check for existing patterns to follow (naming, DI, architecture)
- If this ticket builds or changes UI, find its design reference. Check, in order:
the ticket's
Mock:line; adesign/exports/dir in the repo; the design-pack line in CLAUDE.md. Put the resolved path in the plan's## Design Referencesection. If the ticket touches UI and NO mock exists anywhere, say so in that section explicitly — "no mock found, UI built from spec prose" is a real finding the owner needs to see. - Return the plan draft as text (do NOT write it to disk)
Plan Draft Format
Feature: [name]
Summary
[2-3 sentence description of what this feature does]
Approach
[Architecture decision — why this approach over alternatives]
Success Criteria
- [observable condition that makes this done — a state someone else could check, not "it works"]
- Prover: [the exact check that proves it landed — a field read back, a hash compared, an exit
code, a row count. A
200, a green suite, and "it looked right" are not provers. If nothing in this environment can prove it, name the tool that WOULD and state the result will be ASSERTED, not verified.]
Out of Scope
- [explicitly NOT built here — the adjacent thing a reader would assume is included]
Design Reference
[UI tickets: the mockup path(s) the implementer must build to, e.g.
design/exports/03-editor.png (+ design/exports/light/03-editor.png).
The mock is the visual contract — it wins over prose on any layout dispute.
Non-UI tickets: "n/a — no UI change".
UI ticket with no mock available: "NONE FOUND — UI from spec prose only", and flag it.]
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 First seen · 70 lines · 44 tokens per session scan A 3ce36d5e789f
planner is an agent published in the GitHub repository shashankreddy509/claude-tdd-kit (2 stars, last pushed 13d ago), licensed MIT. It adds 44 tokens to every session and 692 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 agents, from other repositories
quickstart
Agent "quickstart" from generalaction/emdash, covering quickstart, toolchain, core commands, validation commands and important notes.
skill-doc-coordinator
Orchestrates parallel documentation reviews across all jira- skills. Aggregates findings into unified report. Use when running full audit.
test-writer
Writes COMPREHENSIVE tests for all MCP code. ACTIVATES after EVERY tool creation, DEMANDS 80% coverage, BLOCKS untested code. NO MERCY for code without tests.
jira-api-integrator
Integrates Jira API endpoints into MCP tools. ACTIVATE when user mentions "Jira", "issue", "ticket", "API endpoint", "Atlassian", or needs ANY integration with issue tracking. IMMEDIATELY engage for new Jira functionality.
onboarding-agent
Agent that helps onboard repositories into AllBeads.
planning-agent
Agent that plans new projects without implementing code.