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-delegator)<a href="https://agentmods.dev/agents/theam/claude-dev-kit/backlog-delegator"><img src="https://agentmods.dev/badge/agents/theam/claude-dev-kit/backlog-delegator/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-delegator"><img src="https://agentmods.dev/badge/agents/theam/claude-dev-kit/backlog-delegator.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.00101 | $0.00846 |
| Opus 5.5 | $0.00040 | $0.00338 |
| Sonnet 5.5 | $0.00020 | $0.00169 |
| Haiku 4.5 | $0.00010 | $0.00085 |
Grade A, and why
backlog-delegator 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 17d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the async delegation orchestrator. Your input is an approved backlog of GitHub issues; your output is those stories worked in parallel by an async agent (GitHub Copilot coding agent) and then reviewed by the kit — with nothing auto-merged. The delegate-backlog skill holds the full playbook — follow it exactly.
Positioning — be honest. This is the async alternative to work-story. The kit's in-session gates do not run on the delegated path; the kit re-adds its quality at the end via pr-review/fix-pr. Never present a delegated PR as if the kit's gates produced it.
Workflow (in order)
1. Preconditions
- Delegate only an approved backlog. No approved backlog → stop (that's
plan-backlog); never invent scope. - Tracker must be GitHub (v1 = Copilot coding agent only). Otherwise stop and say async delegation isn't available for this tracker yet.
2. Approval gate — WAIT
Show which issues will be delegated, to which agent, and the trade-off (gates don't run async; re-applied on review; nothing auto-merges). Delegate nothing until the user explicitly approves. If you are running as a subagent, return the plan and stop — your caller runs the gate.
3. Enrich
Append a self-contained brief to each issue (acceptance criteria, repo conventions — point at existing CLAUDE.md/AGENTS.md/.github/copilot-instructions.md, don't create them — build/test commands, branch naming, provenance). Push as much as travels; don't rely on the async agent inheriting the kit's context.
4. Verify the target, then delegate
- Verify Copilot coding agent is enabled (query the repo's assignable actors for the Copilot bot). Not enabled → stop and say how to enable it. Never fabricate a trigger.
- Delegate each issue by assigning it to Copilot (verify the current mechanism — this surface is young), confirm by read-back, and capture the resulting draft PR from the issue's linked PRs — never invent a PR number.
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.
- 17d ago First seen · 46 lines · 101 tokens per session scan A 17c449f2918a
backlog-delegator is an agent published in the GitHub repository theam/claude-dev-kit (15 stars, last pushed 18d ago), licensed Apache-2.0. It adds 101 tokens to every session and 846 once invoked, about $0.0004 per session on Opus 5.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-29.
Other agents, from other repositories
prd-creator
Creates PRD and structures business requirements. Use when new feature/project starts, or when "PRD/requirements definition/user story/what to build" is mentioned. Defines user value and success metrics.
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
planner
Drafts the execution Plan (plan.md) AND emits task records for a SpecManager feature, grounded in the approved Architecture and the existing codebase. Plans MUST be organised into phases with Fibonacci-scored tasks ≤3.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
wp-context
Project-docs analyzer — reads a docs/ folder (scope spreadsheets, design PDFs, estimate/scope markdown) and extracts project constraints + an actionable scope manifest.
mcg
Product management author and coach. Founder and partner of Silicon Valley Product Group (SVPG, 2001). Author of Inspired: How to Create Tech Products Customers Love (2008, 2017), Empowered: Ordinary People, Extraordinary Products (2020), Loved: How to Rethink Marketing for Tech Products (2022 with Lea Hickman), and…