agentic-os: Skill for Codex

.agents/skills/subagent-driven-development/SKILL.md

subagent-driven-development is a skill for Codex from KbWen/agentic-os. It costs 20 tokens per session (138 once invoked), scanned A, original, MIT.

A workflow for splitting a large coding task among several helper agents, with agreed inputs, outputs, and hand-off points. An integration checkpoint is a planned moment to combine and check their work.

In plain words
What is it for?
Use it for tasks that can be divided by module or responsibility, such as building separate parts of an application and then combining them.
Why use it?
It reduces the amount of work one agent must handle at once and helps prevent conflicting or incomplete changes. Required checks make problems easier to catch before final integration.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions subagents; installed under .agents/ (shared by several agents).

This is KbWen/agentic-os's own configuration. It tells Codex how to work on agentic-os itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentic-os configures →

Reuse

Borrowing it

Nothing to install: this file belongs to KbWen/agentic-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/KbWen/agentic-os/main/.agents/skills/subagent-driven-development/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/KbWen/agentic-os

Made for: Codex.

Wrote 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.

agentmods badge for subagent-driven-development

README.md
[![agentmods](https://agentmods.dev/badge/skills/kbwen/agentic-os/subagent-driven-development/github.svg)](https://agentmods.dev/skills/kbwen/agentic-os/subagent-driven-development)
Your own site
<a href="https://agentmods.dev/skills/kbwen/agentic-os/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/kbwen/agentic-os/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.

agentmods 80×15 button for subagent-driven-development

Your own site · 80×15
<a href="https://agentmods.dev/skills/kbwen/agentic-os/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/kbwen/agentic-os/subagent-driven-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 138 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.00138
Opus 5.5 $0.00008 $0.00055
Sonnet 5.5 $0.00004 $0.00028
Haiku 4.5 $0.00002 $0.00014

Measured 1mo ago against content hash 96d1736eab31, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.agents/skills/subagent-driven-development/SKILL.md · 23 lines

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

  1. Sub-tasks MUST include testing or checking evidence.
  2. The primary agent is responsible for integration, conflict resolution, and final verification.
  3. Any cross-module changes MUST be announced before integration.
Files

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.

Changes

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.

  1. 1mo ago First seen · 23 lines · 20 tokens per session scan A 96d1736eab31

Subscribe to this mod's changes

subagent-driven-development is a skill published in the GitHub repository KbWen/agentic-os (221 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 138 once invoked, about $0.0001 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-30.

Related

Other skills, from other repositories

agent-config

Use when writing or editing agent configuration, especially permission rules in settings.json, skills, hooks, or MCP servers. Covers the permission-matching behaviour that makes a rule grant more than it reads, and how to check configuration with agentfile.

dennishavermans/agentfile · 51 tokens

muster-frappe-metadata

Design, generate, review, apply, and roll back Frappe or ERPNext metadata changes through Muster. Use for DocTypes, child tables, custom fields, property setters, workflows, roles, permissions, reports, print formats, web pages, workspaces, fixtures, patches, or installed-app compatibility.

musterhq/muster · 69 tokens

muster-frappe-release

Build, seed, deploy, break, measure, and prove a Muster Frappe release. Use for bench or site setup, migrations, realistic ERPNext data, role matrices, browser/mobile QA, performance and recovery tests, release evidence, Frappeverse demos, or normal-speed presentation video.

musterhq/muster · 66 tokens

muster-frappe-security

Threat-model and negatively verify Muster integrations with Frappe OAuth, multi-tenancy, RBAC, field permissions, agent delegation, channels, secrets, approvals, and audit logs. Use for identity linking, site registration, Telegram onboarding, policy changes, permission tests, or security release gates.

musterhq/muster · 64 tokens

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.

musterhq/muster · 65 tokens

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.

musterhq/muster · 66 tokens