Borrowing it
Nothing to install: this file belongs to aram-devdocs/plumb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aram-devdocs/plumb/main/.agents/skills/subagent-driven-development/SKILL.mdgit clone --depth 1 https://github.com/aram-devdocs/plumbWrote 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/aram-devdocs/plumb/subagent-driven-development)<a href="https://agentmods.dev/skills/aram-devdocs/plumb/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/aram-devdocs/plumb/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.
<a href="https://agentmods.dev/skills/aram-devdocs/plumb/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/aram-devdocs/plumb/subagent-driven-development.svg" alt="Reviewed on agentmods" width="80" 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.00059 | $0.02627 |
| Opus 5.5 | $0.00024 | $0.01051 |
| Sonnet 5.5 | $0.00012 | $0.00525 |
| Haiku 4.5 | $0.00006 | $0.00263 |
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 2mo 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subagent-driven development
Execute a plan by dispatching a fresh subagent per task. After each task, run the Plumb review-gate chain. For independent tasks, dispatch in parallel batches for maximum throughput.
Core principle: fresh subagent per task + parallel batches for independent work + ordered review gates = high quality, fast iteration.
When to use
- You have a plan with ≥2 tasks.
- Tasks are mostly independent (different crates, no shared edits, no producer-consumer edges).
- You want to stay in the current session (no context switch).
If tasks are tightly coupled or the plan needs brainstorming, execute manually or use /gh-issue with a single primary.
Process overview
Per task:
Dispatch 01-implementer → self-review → dispatch 02-spec-reviewer → (fixes loop)
→ dispatch 03-code-quality-reviewer → (fixes loop)
→ dispatch 05-architecture-validator → (fixes loop)
→ dispatch 04-test-runner → (fixes loop)
→ (if CDP/MCP/URL/dep touched) dispatch 06-security-auditor in parallel with any of the above
Mark task complete.
After all tasks:
Dispatch a final 04-test-runner pass on the full changeset.
Run `just validate` + `cargo xtask pre-release`.
Parallel batch workflow
Step 1 — task decomposition
For each task, identify:
- Target files — which files will be created / modified.
- Target crates — which of
plumb-core,plumb-format,plumb-cdp,plumb-config,plumb-mcp,plumb-cli,xtaskare touched. - Dependencies — what public items does the task import?
- Outputs — what does the task produce that another might consume (new public API, new MCP tool schema, new config field)?
Step 2 — dependency analysis
Classify each task pair as INDEPENDENT or DEPENDENT.
INDEPENDENT (safe to parallelize) — every one of these must hold:
- Different target files (no shared edits).
- Different crates OR no upward dependency change.
- No change to a shared public API consumed by another task.
- No producer-consumer relationship (one task's public output isn't another's input).
- Can be merged without conflicts.
What ships with it
3 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.
- 2mo ago First seen · 255 lines · 59 tokens per session scan A 01145a7ff726
subagent-driven-development is a skill published in the GitHub repository aram-devdocs/plumb (3 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 59 tokens to every session and 2,627 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-08-31.
Other skills, from other repositories
extract-design
Extract the full design language from any website URL. Produces 8 output files including AI-optimized markdown, visual HTML preview, Tailwind config, React theme, shadcn/ui theme, Figma variables, W3C design tokens, and CSS variables. Also runs WCAG accessibility scoring. Use when user says 'extract design', 'get…
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
design-md-extractor
Extract and document the visual style of public websites as reusable DESIGN.md files. Use when the user asks to analyze a website's design system, extract styles, create design tokens, produce DESIGN.md, generate an agent-readable style guide, or build from a website's visual language.
omd-apply
A skill that applies a project's DESIGN.md file as visual and brand guidance for interface work. It covers components, colors, fonts, layout, copy, motion, and visual assets.
bench-fixture-gen
Generates the shared per-task fixture that every competing arm starts from: a realistic dataset plus an image asset base. Fairness rule: fixtures are generated ONCE per task by this preprocessor and sealed (sha256) before any arm runs; arms never generate their own.
brandmd
Extract a website's design system into a DESIGN.md file. Use when starting a new frontend project, rebuilding a site, or when the user wants AI-generated UI to match an existing brand.