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/kbwen/agentic-os/subagent-driven-developmentnpx skills add KbWen/agentic-os --skill subagent-driven-developmentgit clone --depth 1 https://github.com/KbWen/agentic-osWhat 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.00020 | $0.00138 |
| Opus 5 | $0.00010 | $0.00069 |
| Sonnet 5 | $0.00004 | $0.00028 |
| Haiku 4.5 | $0.00002 | $0.00014 |
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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- subagent-driven-development — 100% identical, 0 lines differ
What it actually says
Subagent-Driven Development
Overview
When a task is splittable, use multiple subagents to process in parallel, accelerating delivery without sacrificing consistency.
Decomposition Strategy
- Split cleanly by module boundaries or responsibilities.
- Define input/output contracts for each sub-task.
- Establish sync checkpoints to avoid integration explosion.
Delivery Requirements
- Sub-tasks MUST include testing or checking evidence.
- The primary agent is responsible for integration, conflict resolution, and final verification.
- Any cross-module changes MUST be announced before integration.
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.
- 2d ago First seen · 23 lines · 20 tokens per session scan A 96d1736eab31
subagent-driven-development is a skill published in the GitHub repository KbWen/agentic-os (149 stars, last pushed 9d ago), licensed MIT. It adds 20 tokens to every session and 138 once invoked, about $0.0001 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
orloj-generator
Interactive scaffold generator for Orloj multi-agent systems. Use this skill whenever someone wants to create, set up, scaffold, bootstrap, or generate an Orloj agent system, pipeline, swarm, or hierarchy. Also trigger when users mention "orlojctl init", ask how to get started with Orloj, want to build a multi-agent…
muster-frappe-workflows
Design and implement durable multi-step Muster workflows for Frappe with agent, subagent, and nested task graphs. Use for workflow definitions, planning, delegation, tool policies, approvals, retries, schedules, triggers, artifacts, dynamic page creation, or Claude-style universal JS and JSON automation.
muster-frappe-orchestrator
Coordinate end-to-end Muster automation work across Frappe or ERPNext architecture, metadata, UI, workflows, security, testing, deployment, and evidence. Use for cross-cutting features, production plans, multi-agent delivery, or work that spans Muster core and a Frappe app.
session-management
Governs the full agent session lifecycle: scratchpad init/close, encoding checkpoint at session start, compaction guard, phase gate protocol, and session summary. USE FOR: starting a new session (prunescratchpad.py --init); writing ## Session Start with governing axiom; managing cross-agent context in .tmp/ / .md…
agent-file-authoring
Encodes the conventions for authoring .agent.md files in .github/agents/: YAML frontmatter requirements, required section headings, relative path rules, cross-reference density, and CI validation. USE FOR: creating or modifying .agent.md role files (VS Code: Custom Agents); diagnosing validateagentfiles.py CI…
rate-limit-resilience
Pre-delegation rate-limit gate workflow with circuit-breaker, provider-aware policies, and audit logging. Implements safe budget checks before orchestration phases.