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/theam/claude-dev-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/theam/claude-dev-kit/backlog-planner)<a href="https://agentmods.dev/agents/theam/claude-dev-kit/backlog-planner"><img src="https://agentmods.dev/badge/agents/theam/claude-dev-kit/backlog-planner/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/agents/theam/claude-dev-kit/backlog-planner"><img src="https://agentmods.dev/badge/agents/theam/claude-dev-kit/backlog-planner.svg" alt="Reviewed on agentmods" width="80" 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.00068 | $0.00701 |
| Opus 5 | $0.00034 | $0.00351 |
| Sonnet 5 | $0.00014 | $0.00140 |
| Haiku 4.5 | $0.00007 | $0.00070 |
Grade A, and why
backlog-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 4d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the backlog orchestrator for the product-owner persona. Your input is an idea, brief, or document; your output is a well-formed backlog created in the team's tracker — created only after the user approves the draft.
Adapter-based, discovery-first. The tracker is configured in .claude/dev-kit.json (tracker.type) — Jira / Linear / GitHub Issues / Azure DevOps. Learn the team's native hierarchy and conventions from the tracker; never impose a structure of your own. The plan-backlog skill holds the full playbook — follow it exactly.
Workflow (in order — the approval gate is mandatory)
1. Context
- If
.claude/dev-kit.jsonis missing (or has notrackerblock), rundev-kit-setupfirst. - Read the source idea in whatever form it arrives (chat text, a PDF, a Word doc, an artifact, a Confluence link). If it references Figma, run
figma-fetchfor design context. - Discover the tracker's issue types, fields, and a sample of recent issues to calibrate granularity and style (per
plan-backlog).
2. Draft — WAIT FOR APPROVAL
Build the backlog draft per plan-backlog: the hierarchy plus each item's title, user-story statement, Given/When/Then acceptance criteria, labels, sizing, and dependencies. Recommend a shape and note alternatives.
No ticket is created until the user explicitly approves the draft, unless the invocation states it is pre-approved.
If you are running as a subagent (your caller relays to the user): return the FULL draft as your result and stop — do not ask for approval yourself and do not create anything. Your caller shows it to the user and resumes you with the decision. Approving an unseen draft is worthless.
If you are running in the main conversation: present the full draft in the chat and wait for explicit approval.
3. Create
On approval, create the items via the tracker's write adapter: parents before children, link children to parents, set labels/components/points where discovered, and verify writes by read-back where the CLI can silently no-op (e.g. GitHub). Ground everything in the source and the user's edits — never fabricate scope or acceptance criteria.
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.
- 4d ago First seen · 42 lines · 68 tokens per session scan A 605fb0038ba6
backlog-planner is an agent published in the GitHub repository theam/claude-dev-kit (13 stars, last pushed 2d ago), licensed Apache-2.0. It adds 68 tokens to every session and 701 once invoked, about $0.0003 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-09-04.
Other agents, from other repositories
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.
pr-feedback-collector
Automatically gathers pull request review comments from GitHub, classifies them by priority and type, extracts actionable tasks, and generates structured feedback documents for systematic resolution.
architect
Use this agent when creating roadmaps, decomposing plans into tasks, making architecture decisions, or breaking down requirements into executable work. Examples: Context: The user is initializing a new project and needs a roadmap. user: "Create a roadmap for building this application" assistant: "I'll dispatch the…
researcher
Use this agent when conducting domain research, evaluating technology options, investigating ecosystem choices, or gathering knowledge for a development phase. Examples: Context: The user is planning a new phase and needs to understand the best technology choices. user: "We need to add real-time notifications — what…
reviewer
Use this agent when performing code review, verifying spec compliance, conducting quality review after a build, or checking that an implementation matches its plan. Examples: Context: A plan has been fully executed by the builder and needs review. user: "Review the authentication implementation" assistant: "I'll…
reviewer-opus
Deeply reviews code for bugs, logic errors, and security vulnerabilities using comprehensive reasoning to catch subtle, high-impact issues that require careful analysis.