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 skills add theam/claude-dev-kit --skill plan-backloggit 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/skills/theam/claude-dev-kit/plan-backlog)<a href="https://agentmods.dev/skills/theam/claude-dev-kit/plan-backlog"><img src="https://agentmods.dev/badge/skills/theam/claude-dev-kit/plan-backlog/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/skills/theam/claude-dev-kit/plan-backlog"><img src="https://agentmods.dev/badge/skills/theam/claude-dev-kit/plan-backlog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00080 | $0.01593 |
| Opus 5 | $0.00040 | $0.00796 |
| Sonnet 5 | $0.00016 | $0.00319 |
| Haiku 4.5 | $0.00008 | $0.00159 |
Grade A, and why
plan-backlog 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Backlog
Turn a product idea into a structured, well-formed backlog in the team's tracker — the upstream half of the issue-to-PR workflow, for the product-owner persona. It closes the loop idea → backlog → ticket → PR (created stories feed straight into work-story).
This is the write counterpart to issue-fetch (which reads). Nothing is created until you approve the draft.
Trigger
A request to turn an idea / brief / description / document into tickets, epics, or a backlog — e.g. "draft stories for this feature", "create Jira tickets from this doc", "break this initiative into a backlog".
Project configuration
Read .claude/dev-kit.json at the consuming repo root. The tracker block names the active adapter and its settings:
{ "tracker": { "type": "jira" | "linear" | "github" | "azure", ... } }
If the file does not exist (or has no tracker block), run dev-kit-setup first — it detects the tracker and persists the config, then returns here. Don't ask for values setup can discover.
1. Intake — read the idea in whatever form it arrives
- Pasted text / chat description → use directly.
- PDF → read it (page range as needed).
- Word (
.docx) → not natively readable; convert first (textutil -convert txt file.docx -output -on macOS, orpandoc file.docx -t markdown), then read. If neither tool is available, ask the user to paste the text or export a PDF. - Artifact / Confluence page / URL → fetch it.
- Figma link (
figma.com/(design|file)/…) → runfigma-fetchfor design context.
Work only from what the source says plus what the user confirms — never invent scope or acceptance criteria.
2. Discovery-first — learn the team's hierarchy and conventions
Don't impose a structure; mirror the team's. Using the adapter for tracker.type, discover:
- the issue types available and their hierarchy (Epic / Story / Task / Feature / Sub-task, …),
- the fields that matter (acceptance criteria, story points/estimate, epic/parent link, labels, components),
- a sample of recent issues to calibrate granularity and writing style.
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 · 98 lines · 80 tokens per session scan A 1758f7150621
plan-backlog is a skill published in the GitHub repository theam/claude-dev-kit (13 stars, last pushed 3d ago), licensed Apache-2.0. It adds 80 tokens to every session and 1,593 once invoked, about $0.0004 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 skills, from other repositories
x-dev
A development workflow for completing tasks from a task folder. It follows the task's README and checklist, implements work in dependency order, and records verification evidence.
x-req
A requirements planner that turns a confirmed request into a ready-to-build task package. It assigns a risk level from Q0 to Q3, where higher levels cover changes such as permissions, public interfaces, data migrations, or concurrency.
deliver-task
Drive one READY task end-to-end — implement in a worktree, independent adversarial review, bounded 3-iteration patch loop, then hand to a human for merge. Pass the issue number, e.g. "/deliver-task 42". A single-command composition of next-task + review-task + patch-task.
silver:triage
Generic review-finding triage across any artifact or scope — classifies findings, files valid issues via PM adapter, and routes fixes without reviewer self-triage.
silver-review-triage
Specialized review-response wrapper — delegates to generic /sb:triage for finding classification, PM filing, and fix routing after code or artifact review.
sb:review-triage
Specialized review-response wrapper — delegates to generic /sb:triage for finding classification, PM filing, and fix routing after code or artifact review.