subagent-driven-development

subagent-driven-development is a skill for Claude Code from obra/superpowers. It costs 17 tokens per session (7,533 once invoked), scanned C, original, MIT.

A development workflow for carrying out an implementation plan with separate coding and review agents. Each task is implemented independently, reviewed for requirements and code quality, and followed by a broader final review.

In plain words
What is it for?
It is for executing multi-step coding plans, delegating independent tasks, checking each result, and reviewing the finished branch.
Why use it?
It provides focused review at each stage and helps catch both task-level mistakes and problems across the completed work.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is "Dispatch final code reviewer (../requesting-code-review/code-reviewer.md)" [shape=box];.

Part of the superpowers plugin — 15 skills, 1 hook shipped together

Good fit It is for executing multi-step coding plans, delegating independent tasks, checking each result, and reviewing the finished branch.

Compare 6 skills from other repositories ↓
About the project

Superpowers is a software development methodology for coding agents that guides work from clarifying requirements through design, planning, implementation, testing, and review. It is for developers who want agents to follow a structured, test-focused process using composable skills and subagents.

obra/superpowers · 299,875 stars · on GitHub

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/obra/superpowers
agentmods
npx agentmods add skills/obra/superpowers/subagent-driven-development

Made for: Claude Code.

Or install superpowers, the plugin that ships this one along with the rest of its 15 skills, 1 hook.

Wrote 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.

agentmods badge for subagent-driven-development

README.md
[![agentmods](https://agentmods.dev/badge/skills/obra/superpowers/subagent-driven-development/github.svg)](https://agentmods.dev/skills/obra/superpowers/subagent-driven-development)
Your own site
<a href="https://agentmods.dev/skills/obra/superpowers/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/obra/superpowers/subagent-driven-development/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.

agentmods 80×15 button for subagent-driven-development

Your own site · 80×15
<a href="https://agentmods.dev/skills/obra/superpowers/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/obra/superpowers/subagent-driven-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,533 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe. ✓ AI security review Fable 5.1 · 6 Sept 2026 📄 Read the review Third-party audits
  • Socket pass 19 Sept 2026
  • Snyk pass 19 Sept 2026
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Tool Misuse · line 153
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • medium Rogue Agent · line 511
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.07533
Opus 5.5 $0.00007 $0.03013
Sonnet 5.5 $0.00003 $0.01507
Haiku 4.5 $0.00002 $0.00753

Measured 26d ago against content hash 8dde5589ee08, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

subagent-driven-development scanned grade C with 1 finding 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 26d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

delete this plan's workspace (`rm -rf <workspace>`) — the git history is
Origin

Copies of this mod

8 near-identical copies found in the catalogue:

skills/subagent-driven-development/SKILL.md · 569 lines

How it starts

The opening of the file, as written. The whole thing — 569 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Subagent-Driven Development

Execute plan by dispatching a fresh implementer subagent per task, a task review (spec compliance + code quality) after each, and a broad whole-branch review at the end.

Why subagents: You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work.

Core principle: Fresh subagent per task + task review (spec + quality) + broad final review = high quality, fast iteration

Narration: between tool calls, narrate at most one short line — the ledger and the tool results carry the record.

Continuous execution: Do not pause to check in with your human partner between tasks. Execute all tasks from the plan without stopping. The only reasons to stop are the four named below, or all tasks complete. "Should I continue?" prompts and progress summaries waste their time — they asked you to execute the plan, so execute it.

Rulings, not stalls. A running plan does not wait on a human. Conflicts, ambiguities, plan defects, a cap you would have asked to exceed — decide them. The spec is the binding authority, the plan is its argument, and your judgment settles what neither answers. Record every decision in the ledger as Ruling: <what you decided> — <why> — <what it costs if wrong>, and keep going. A wrong ruling costs rework your human partner can see and undo; a session parked on a question costs their whole day and buys nothing.

Four things stop you, and only these: an irreversible or destructive operation; a security-sensitive action; a side effect outside this worktree that norms say you ask about first (a merge, a push to a shared branch, a publish); and a plan so broken that every path forward is a guess. For those, stop and ask.

When to Use

digraph when_to_use {
    "Have implementation plan?" [shape=diamond];
    "Tasks mostly independent?" [shape=diamond];
    "Partner chose inline, or no subagent tool?" [shape=diamond];
    "subagent-driven-development" [shape=box];
    "executing-plans" [shape=box];
    "Manual execution or brainstorm first" [shape=box];

    "Have implementation plan?" -> "Tasks mostly independent?" [label="yes"];
    "Have implementation plan?" -> "Manual execution or brainstorm first" [label="no"];
    "Tasks mostly independent?" -> "Partner chose inline, or no subagent tool?" [label="yes"];
    "Tasks mostly independent?" -> "Manual execution or brainstorm first" [label="no - tightly coupled"];
    "Partner chose inline, or no subagent tool?" -> "executing-plans" [label="yes"];
    "Partner chose inline, or no subagent tool?" -> "subagent-driven-development" [label="no"];
}

Read the full file on GitHub · 569 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 26d ago Changed 8dde5589ee08
  2. 1mo ago First seen · 569 lines · 17 tokens per session scan C 8dd1b8e698ed

Subscribe to this mod's changes

subagent-driven-development is a skill published in the GitHub repository obra/superpowers (299,875 stars, last pushed 6d ago), licensed MIT. It adds 17 tokens to every session and 7,533 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

skill-creator

Create a skill or bring an existing one up to the same standard (validate + asm eval fix loop); run evals, tune triggering. Use when authoring, fixing, or retrofitting a skill. Don't use for invoking skills, writing prose, or Python scaffolds.

luongnv89/asm · 60 tokens

skill-index-updater

Add GitHub skill repos to the ASM index: clone, audit, eval, regenerate index, rebuild catalog, open PR. Use when given GitHub URLs to onboard. Don't use for refreshing indexed repos (refresh-index), improving skills (skill-creator), or install.

luongnv89/asm · 59 tokens

hello-world

A minimal test skill that greets the user and demonstrates the ASM publish workflow.

luongnv89/asm · 19 tokens

typescript

You MUST use this when working on TypeScript-specific problems - compiler errors, tsconfig, strict typing, type inference, generics, complex type definitions, module resolution, ESM/CJS interoperability, type-checking performance, migration, or monorepo configuration. Also applies to designing or refactoring type-safe…

sentimony/skills · 96 tokens

debugging

You MUST use this when investigating bugs, regressions, failing tests, build or integration failures, flaky behavior, performance anomalies, or other unexpected technical behavior.

sentimony/skills · 34 tokens

parallel-agents

You MUST use this when several units of work might run concurrently through agents - independent investigations, specialist reviews, repository analyses, or plan tasks that look unrelated - covering whether they are genuinely independent, which mutable state needs isolation, how wide the wave should be, and how…

sentimony/skills · 64 tokens