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 Eilodon/DPS-Superskills-MCP --skill subagent-driven-developmentgit clone --depth 1 https://github.com/Eilodon/DPS-Superskills-MCPWrote 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/eilodon/dps-superskills-mcp/subagent-driven-development)<a href="https://agentmods.dev/skills/eilodon/dps-superskills-mcp/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/eilodon/dps-superskills-mcp/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.00039 | $0.01353 |
| Opus 5 | $0.00019 | $0.00677 |
| Sonnet 5 | $0.00008 | $0.00271 |
| Haiku 4.5 | $0.00004 | $0.00135 |
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 6d 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 — 179 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 three-stage review after each: spec compliance → code quality → specialist lens (STRIDE/OWASP/ATAM/TEMPORAL/CPT).
Core principle: Fresh subagent per task + evidence-gated review = high quality, fast iteration.
Continuous execution: Do not pause between tasks. Execute all tasks without stopping unless: BLOCKED status unresolvable, genuine ambiguity, or all tasks complete.
Announce: "Using subagent-driven-development to execute the plan."
Pre-Check
# Confirm isolated workspace exists
git worktree list
# If not — run using-git-worktrees first
Read plan from docs/superskills/plans/ once. Extract all tasks.
Create task tracker:
- Claude Code:
TodoWritetool - Other harnesses: maintain
- [ ]checklist inline in this session - Fallback:
echo "[ ] Task N: <name>" >> /tmp/task-tracker.txt
Per-Task Loop
For each task:
1. Dispatch implementer subagent (full task text + context)
2. Answer questions if asked BEFORE implementation
3. Implementer: implements, tests, commits, self-reviews
4. Stage A: Spec compliance review (spec reviewer subagent)
→ issues found? implementer fixes → re-review → repeat until ✅
5. Stage B: Code quality review (quality reviewer subagent)
→ issues found? implementer fixes → re-review → repeat until ✅
6. Stage C: specialist-review (context-aware lens)
→ CRITICAL? fix immediately. HIGH? fix before next task.
→ Bug confirmed? trigger pattern-globalize before proceeding.
7. verification-before-completion gate — evidence anchor required
8. Mark task complete in TodoWrite
Do NOT start Stage B before Stage A is ✅. Do NOT mark task complete before verification-before-completion.
Subagent Context Templates
Implementer
TASK: [Full task text from plan]
PLAN: [Feature goal + architecture from plan header]
CODEBASE: [Relevant file structure]
CONSTRAINTS: Follow tdd-verified. No implementation before failing test.
No completion claim without verification-before-completion.
STATUS: Report one of: DONE | DONE_WITH_CONCERNS | NEEDS_CONTEXT | BLOCKED
What ships with it
1 file 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.
- 6d ago First seen · 179 lines · 39 tokens per session scan A 5d566c3c7334
subagent-driven-development is a skill published in the GitHub repository Eilodon/DPS-Superskills-MCP (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,353 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…