subagent-driven-development

subagent-driven-development is a skill for Claude Code from guanyang/open-agent-hub. It costs 17 tokens per session (7,533 once invoked), scanned C, a copy of subagent-driven-development, MIT.

A development workflow that assigns each implementation task to a fresh helper agent, reviews the task afterward, and performs a final review of the whole change.

In plain words
What is it for?
Use it to carry out multi-step implementation plans with separate task implementers, reviewers, and a final branch review.
Why use it?
It keeps each helper focused with only the context it needs and adds checks for both requirement compliance and code quality.

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 open-agent-hub plugin — 105 skills, 3 commands, 5 agents, 6 MCP servers shipped together

Good fit Use it to carry out multi-step implementation plans with separate task implementers, reviewers, and a final branch review.

Compare 6 skills from other repositories ↓
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/guanyang/open-agent-hub
agentmods
npx agentmods add skills/guanyang/open-agent-hub/subagent-driven-development

Made for: Claude Code.

Or install open-agent-hub, the plugin that ships this one along with the rest of its 105 skills, 3 commands, 5 agents, 6 MCP servers.

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/guanyang/open-agent-hub/subagent-driven-development/github.svg)](https://agentmods.dev/skills/guanyang/open-agent-hub/subagent-driven-development)
Your own site
<a href="https://agentmods.dev/skills/guanyang/open-agent-hub/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/guanyang/open-agent-hub/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/guanyang/open-agent-hub/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/guanyang/open-agent-hub/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.
Origin 100% copy Near-identical to another mod 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

This is a copy

100% identical to subagent-driven-development — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

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

8 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 guanyang/open-agent-hub (979 stars, last pushed 3d 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). It is 100% identical to subagent-driven-development, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

check

Reviews diffs, PRs, release readiness, and publishing follow-through. Use when asked to review, triage issues or PRs, or ship. Not for debugging root causes or prose.

tw93/Waza · 41 tokens

fable-validate-loop

Use when the user asks to validate a GitHub issue with Fable 5.1 and then autonomously drive it to a reviewed PR in one shot — "fable-validate-loop", "fable validate and work on #N", "fully automate issue #N with fable". Runs fable-validate, auto-applies its update-issue edits when the verdict calls for it, has…

richkuo/rk-skills · 219 tokens

project-onboarding

Standard procedure for onboarding new software projects: Feature analysis, code quality review, onboarding checklist, and task creation.

ellmos-ai/skills · 26 tokens

skill-register-care

Pflege-Skill, der das dreiteilige Skill-Register konsistent hält (code-skill-index-Kataloge, Skill-Index, SKILL-MAP Family-/Routing-Map). Nutze diesen Skill für einen Drift-Check zwischen dem realen Skill-Inventar und dem dokumentierten Register: fehlende oder zu viele Einträge melden, Counts korrigieren, Stand-Datum…

ellmos-ai/skills · 117 tokens

herdr-dispatch

Run a task list across parallel Herdr panes - measure the pane budget, split, start one agent per task, brief them, collect results from files, handle blocked workers, clean up. Use when the user says "dispatch these", "run these in parallel", "fan this out", "spin up agents", "/herdr-dispatch", or whenever the…

pivoshenko/pivoshenko.ai · 126 tokens

git-issue-create

Open one standalone GitHub issue with gh - duplicate-checked first, conventional title, repo-template-aware body, auto-resolved labels. Use for every issue-filing request however casual: "open an issue", "file a bug", "make a ticket", "/git-issue-create", "track this", "note this down", "we should fix X later", or…

pivoshenko/pivoshenko.ai · 157 tokens