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 agentmods add skills/mick-gsk/drift/subagent-driven-developmentnpx skills add mick-gsk/drift --skill subagent-driven-developmentgit clone --depth 1 https://github.com/mick-gsk/driftWrote 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/mick-gsk/drift/subagent-driven-development)<a href="https://agentmods.dev/skills/mick-gsk/drift/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/mick-gsk/drift/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 | $0.00037 | $0.00697 |
| Opus 5 | $0.00018 | $0.00349 |
| Sonnet 5 | $0.00007 | $0.00139 |
| Haiku 4.5 | $0.00004 | $0.00070 |
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 3d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subagent-Driven Development
Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review.
Core principle: Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration
When to Use
- You have an implementation plan (from writing-plans skill)
- Tasks are mostly independent
- You want to stay in this session
vs. Executing Plans: Same session, fresh context per task, faster iteration with no human-in-loop between tasks.
The Process
- Read plan once — extract all tasks with full text and context
- Create TodoWrite with all tasks
- Per task:
- Dispatch implementer subagent with full task text + scene-setting context
- Answer any questions before letting them proceed
- Implementer implements, tests, commits, self-reviews
- Dispatch spec compliance reviewer subagent
- If spec issues found: implementer fixes → re-review
- Dispatch code quality reviewer subagent
- If quality issues found: implementer fixes → re-review
- Mark task complete
- After all tasks: dispatch final code reviewer for entire implementation
- Use
superpowers:finishing-a-development-branch
Model Selection
- Mechanical tasks (isolated functions, clear specs, 1-2 files): cheap/fast model
- Integration tasks (multi-file, pattern matching, debugging): standard model
- Architecture/design/review: most capable model
Handling Implementer Status
- DONE: Proceed to spec compliance review
- DONE_WITH_CONCERNS: Read concerns before proceeding. Address correctness/scope concerns first.
- NEEDS_CONTEXT: Provide missing context and re-dispatch
- BLOCKED: Assess blocker — more context, more capable model, smaller task, or escalate to human
Never ignore an escalation or force the same model to retry without changes.
Prompt Templates
./implementer-prompt.md— Dispatch implementer subagent./spec-reviewer-prompt.md— Dispatch spec compliance reviewer subagent./code-quality-reviewer-prompt.md— Dispatch code quality reviewer subagent
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.
- 3d ago First seen · 76 lines · 37 tokens per session scan A 6ad14b968982
subagent-driven-development is a skill published in the GitHub repository mick-gsk/drift (14 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 697 once invoked, about $0.0002 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-30.
Other skills, from other repositories
truecourse-hooks
Install, configure, or remove the TrueCourse pre-commit hook.
truecourse-list
List TrueCourse violations found in this repository.
code-quality-review
Run a maintainability and structure review focused on abstraction quality, branching complexity, file growth, canonical ownership, duplication, and refactoring opportunities. Use when the user asks for code quality review, maintainability review, 代码质量审查, 可维护性审查, or comments about whether the change stays easy to…
optimization-audit
Comprehensive optimization audit with two modes and a single tier. Planning mode designs performance strategy, capacity planning, and scaling architecture. Audit mode scans code and infrastructure for performance anti-patterns, inefficient algorithms, N+1 queries, missing caching, concurrency issues, and resource…
scan
Scan a project with sentrux to get structural health grades (A-F) across 14 dimensions including coupling, cycles, cohesion, dead code, and test coverage. Use when the user wants to check code quality, architecture health, or before/after an agent session.
cognitive-interface-audit
Comprehensive cognitive interface audit with two modes and a single tier. Planning mode designs task models, user expertise mapping, and error tolerance strategy. Audit mode evaluates mental model alignment (Norman's Gulfs), consistency (Gestalt), error tolerance (Wood 7-layer defense), cognitive load (NASA-TLX…