subagent-driven-development

subagent-driven-development is a skill for Claude Code from itallstartedwithaidea/agent-skills. It costs 38 tokens per session (1,262 once invoked), scanned A, original, MIT.

A development workflow that gives each coding task a fresh helper agent and checks its work in two review stages before merging it. A subagent is a separate helper process assigned to one focused task.

In plain words
What is it for?
It helps split larger implementation tasks into smaller assignments, run them in isolation, review the results, and merge accepted changes.
Why use it?
It limits confusion from long conversations and prevents unrelated tasks from sharing stale assumptions. The reviews check both whether the requested work was completed and whether the code is maintainable.

Skill for Claude Code

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

Part of the software-dev-skills plugin — 8 skills shipped together , and of all-skills

Good fit It helps split larger implementation tasks into smaller assignments, run them in isolation, review the results, and merge accepted changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/itallstartedwithaidea/agent-skills/subagent-driven-development
Install

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.

Any agent
npx skills add itallstartedwithaidea/agent-skills --skill subagent-driven-development
Clone the repo
git clone --depth 1 https://github.com/itallstartedwithaidea/agent-skills

Made for: Claude Code.

Or install software-dev-skills, the plugin that ships this one along with the rest of its 8 skills.

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/itallstartedwithaidea/agent-skills/subagent-driven-development/github.svg)](https://agentmods.dev/skills/itallstartedwithaidea/agent-skills/subagent-driven-development)
Your own site
<a href="https://agentmods.dev/skills/itallstartedwithaidea/agent-skills/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/itallstartedwithaidea/agent-skills/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/itallstartedwithaidea/agent-skills/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/itallstartedwithaidea/agent-skills/subagent-driven-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,262 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00038 $0.01262
Opus 5.5 $0.00015 $0.00505
Sonnet 5.5 $0.00008 $0.00252
Haiku 4.5 $0.00004 $0.00126

Measured 1mo ago against content hash 8623a62a78cb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

subagent-driven-development 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 1mo 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.

skills/software-dev/subagent-driven-development/SKILL.md · 131 lines

How it starts

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

Subagent-Driven Development

Part of Agent Skills™ by googleadsagent.ai™

Description

Subagent-Driven Development dispatches each discrete task to a fresh subagent with a clean context window, then subjects the output to a two-stage review before merging. The orchestrating agent decomposes work into atomic units, writes precise specifications for each, and spawns isolated subagents that cannot pollute each other's context or carry forward stale assumptions.

Context window contamination is the silent killer of agent code quality. As a conversation grows, early instructions fade, variable names blur, and the agent begins referencing code that has since been refactored. By giving each task a fresh subagent, every implementation starts from a clean slate with only the relevant specification and referenced files. The result is consistently high-quality output regardless of session length.

The two-stage review process catches defects at different abstraction levels. Stage 1 verifies spec compliance: does the output do what was asked? Stage 2 evaluates code quality: is it well-structured, tested, and maintainable? Only code that passes both gates is accepted into the codebase.

Use When

  • A task can be decomposed into 3+ independent subtasks
  • The conversation context has grown large enough to risk coherence loss
  • Multiple files or modules must be modified in parallel
  • You need best-of-N attempts for a complex implementation
  • Quality gates must be enforced consistently across all outputs
  • The user requests parallel or isolated task execution

How It Works

graph TD
    A[Orchestrator: Decompose Task] --> B[Write Spec for Subtask 1]
    A --> C[Write Spec for Subtask 2]
    A --> D[Write Spec for Subtask N]
    B --> E[Spawn Subagent 1]
    C --> F[Spawn Subagent 2]
    D --> G[Spawn Subagent N]
    E --> H[Stage 1: Spec Compliance Review]
    F --> H
    G --> H
    H --> I{Passes?}
    I -->|No| J[Return to Subagent with Feedback]
    J --> H
    I -->|Yes| K[Stage 2: Code Quality Review]
    K --> L{Passes?}
    L -->|No| J
    L -->|Yes| M[Merge to Main Branch]

Read the full file on GitHub · 131 lines

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. 1mo ago First seen · 131 lines · 38 tokens per session scan A 8623a62a78cb

Subscribe to this mod's changes

subagent-driven-development is a skill published in the GitHub repository itallstartedwithaidea/agent-skills (44 stars, last pushed 6mo ago), licensed MIT. It adds 38 tokens to every session and 1,262 once invoked, about $0.0002 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-03.

Related

Other skills, from other repositories

review-stack

Stack review of one or more third-party tools (OXC, TanStack, Vite, cf, Sentry, pnpm, Claude Code...) against current official best practices, or of what a dependency bump brings (bumped): one parallel subagent per tool, verified findings, one consolidated plan in chat. USE WHEN: user runs /review-stack or explicitly…

louisbrulenaudet/monorepo-template · 115 tokens

review

Code and design review of this repo by domain - architecture, ci, code-quality, configuration, performance, security, seo, simplicity, tests, ui: one parallel reviewer subagent per selected domain, verified findings, one consolidated plan in chat with IDs to answer. USE WHEN: user runs /review, optionally with domains…

louisbrulenaudet/monorepo-template · 131 tokens

ad-delivery-review

A Chinese-language quality review and retrospective guide for advertising proposals, presentation outlines, campaign plans, strategy documents, and client pitches.

ilexlyu/ad-proposal-skills · 81 tokens

tool-defs-analysis

Read-only audit of MCP definition language across an existing surface — tools, resources, prompts, server instructions. Walks every definition file and checks 16 categories the LLM reads to decide whether and how to call: voice & tense, internal leaks, audience leaks, defaults, recovery hints, field descriptions…

cyanheads/mcp-ts-core · 177 tokens

release-pr-review

Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…

cyanheads/mcp-ts-core · 136 tokens

code-simplifier

Cleanup pass that edits the working tree — over a session's uncommitted changes, or a named path or whole codebase. Reads git diff (or the named target) and simplifies, consolidates, and aligns code with the existing codebase — modernize syntax, cut unnecessary complexity and slop, consolidate duplicated logic, catch…

cyanheads/mcp-ts-core · 160 tokens