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 brunob54/superpowers-orchestrator --skill subagent-driven-developmentgit clone --depth 1 https://github.com/brunob54/superpowers-orchestratorWrote 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/brunob54/superpowers-orchestrator/subagent-driven-development)<a href="https://agentmods.dev/skills/brunob54/superpowers-orchestrator/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/brunob54/superpowers-orchestrator/subagent-driven-development.svg" alt="Measured on agentmods" 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.00108 | $0.06860 |
| Opus 5 | $0.00054 | $0.03430 |
| Sonnet 5 | $0.00022 | $0.01372 |
| Haiku 4.5 | $0.00011 | $0.00686 |
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 7d 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 — 483 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subagent-Driven Development
Execute a plan with fresh subagents per task and strict review gates.
Required Start
Announce: I'm using subagent-driven-development to execute this plan.
Core Flow
digraph sdd_process {
rankdir=TB;
subgraph cluster_per_task {
label="Per Task";
"Record BASE, write task brief, dispatch implementer" [shape=box];
"Implementer asks questions?" [shape=diamond];
"Answer questions, provide context" [shape=box];
"Implementer implements, tests, self-reviews, writes report file" [shape=box];
"Generate review package, dispatch task reviewer" [shape=box];
"Spec ✅ and quality approved?" [shape=diamond];
"Dispatch fix subagent (spec + quality findings together)" [shape=box];
"Mark task complete, append ledger line" [shape=box];
}
"Read plan, extract all tasks, create tracking" [shape=box];
"More tasks?" [shape=diamond];
"Final whole-branch review loop (multi-code-review)" [shape=box];
"Shut down spawned subagents" [shape=box];
"Invoke finishing-a-development-branch" [shape=doublecircle];
"Read plan, extract all tasks, create tracking" -> "Record BASE, write task brief, dispatch implementer";
"Record BASE, write task brief, dispatch implementer" -> "Implementer asks questions?";
"Implementer asks questions?" -> "Answer questions, provide context" [label="yes"];
"Answer questions, provide context" -> "Record BASE, write task brief, dispatch implementer";
"Implementer asks questions?" -> "Implementer implements, tests, self-reviews, writes report file" [label="no"];
"Implementer implements, tests, self-reviews, writes report file" -> "Generate review package, dispatch task reviewer";
"Generate review package, dispatch task reviewer" -> "Spec ✅ and quality approved?";
"Spec ✅ and quality approved?" -> "Dispatch fix subagent (spec + quality findings together)" [label="no"];
"Dispatch fix subagent (spec + quality findings together)" -> "Generate review package, dispatch task reviewer" [label="re-review"];
"Spec ✅ and quality approved?" -> "Mark task complete, append ledger line" [label="yes"];
"Mark task complete, append ledger line" -> "More tasks?";
"More tasks?" -> "Record BASE, write task brief, dispatch implementer" [label="yes"];
"More tasks?" -> "Final whole-branch review loop (multi-code-review)" [label="no"];
"Final whole-branch review loop (multi-code-review)" -> "Shut down spawned subagents";
"Shut down spawned subagents" -> "Invoke finishing-a-development-branch";
}
What ships with it
5 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.
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.
- 7d ago First seen · 483 lines · 108 tokens per session scan A 1d90b6a9c530
subagent-driven-development is a skill published in the GitHub repository brunob54/superpowers-orchestrator (3 stars, last pushed yesterday), licensed MIT. It adds 108 tokens to every session and 6,860 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
github-pr-review
Handles PR review comments and feedback resolution. Use when user wants to resolve PR comments, handle review feedback, fix review comments, address PR review, check review status, respond to reviewer, verify PR readiness, review PR comments, analyze review feedback, evaluate PR comments, assess review suggestions, or…
privacy-guard
Prevents private infrastructure details (node hostnames, internal project names, local usernames and personal emails, absolute home paths, private and VPN IP ranges) from leaking into public repositories through commits, PRs, docs or release artifacts. Use when working in a public or soon-to-be-public repo, before…
github-pr-merge
Merges GitHub Pull Requests after validating pre-merge checklist. Use when user wants to merge PR, close PR, finalize PR, complete merge, approve and merge, or execute merge. Runs pre-merge validation (tests, lint, CI, comments), confirms with user, merges with proper format, handles post-merge cleanup.
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
git-commit
Creates git commits following Conventional Commits format with type/scope/subject. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md.
assess
Issue triage and status assessment - analyze current state, detect health signals, and recommend next action with full workflow plan.