subagent-driven-development

subagent-driven-development is a skill for Claude Code, Codex from moltis-org/moltis. It costs 32 tokens per session (2,212 once invoked), scanned A, a copy of subagent-driven-development, MIT.

A workflow for carrying out an implementation plan by assigning separate tasks to fresh coding agents and reviewing each task in two stages.

In plain words
What is it for?
It helps execute multi-step plans when tasks are mostly independent and need review for specification compliance and code quality.
Why use it?
It reduces confusion between tasks and adds independent checks for whether the work matches the requirements and meets quality standards.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for hermes-agent. Also seen: mentions subagents; built for hermes-agent.

Good fit It helps execute multi-step plans when tasks are mostly independent and need review for specification compliance and code quality.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/moltis-org/moltis/subagent-driven-development
About the project

Moltis is a persistent personal agent server written in Rust that runs on hardware controlled by its user. It provides an AI agent with sandboxed command execution, model-provider connections, memory, voice, scheduling, messaging integrations, browser automation, and MCP tools. Its catalogue add-ons extend the agent’s workflows and available tools.

moltis-org/moltis · 2,851 stars · on GitHub · moltis.org

Install

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.

Any agent
npx skills add moltis-org/moltis --skill subagent-driven-development
Clone the repo
git clone --depth 1 https://github.com/moltis-org/moltis

Made for: Claude Code, 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/moltis-org/moltis/subagent-driven-development/github.svg)](https://agentmods.dev/skills/moltis-org/moltis/subagent-driven-development)
Your own site
<a href="https://agentmods.dev/skills/moltis-org/moltis/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/moltis-org/moltis/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/moltis-org/moltis/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/moltis-org/moltis/subagent-driven-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,212 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.
Origin 81% copy Near-identical to another mod 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.00032 $0.02212
Opus 5 $0.00016 $0.01106
Sonnet 5 $0.00006 $0.00442
Haiku 4.5 $0.00003 $0.00221

Measured 9d ago against content hash ef66a4392fb8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, 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 9d 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

This is a copy

81% identical to subagent-driven-development — 31 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

crates/skills/src/assets/software-development/subagent-driven-development/SKILL.md · 340 lines

How it starts

The opening of the file, as written. The whole thing — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Subagent-Driven Development

Overview

Execute implementation plans by dispatching fresh subagents per task with systematic two-stage review.

Core principle: Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration.

When to Use

Use this skill when:

  • You have an implementation plan (from writing-plans skill or user requirements)
  • Tasks are mostly independent
  • Quality and spec compliance are important
  • You want automated review between tasks

vs. manual execution:

  • Fresh context per task (no confusion from accumulated state)
  • Automated review process catches issues early
  • Consistent quality checks across all tasks
  • Subagents can ask questions before starting work

The Process

1. Read and Parse Plan

Read the plan file. Extract ALL tasks with their full text and context upfront. Create a todo list:

# Read the plan
read_file("docs/plans/feature-plan.md")

# Create todo list with all tasks
todo([
    {"id": "task-1", "content": "Create User model with email field", "status": "pending"},
    {"id": "task-2", "content": "Add password hashing utility", "status": "pending"},
    {"id": "task-3", "content": "Create login endpoint", "status": "pending"},
])

Key: Read the plan ONCE. Extract everything. Don't make subagents read the plan file — provide the full task text directly in context.

2. Per-Task Workflow

For EACH task in the plan:

Step 1: Dispatch Implementer Subagent

Use delegate_task with complete context:

delegate_task(
    goal="Implement Task 1: Create User model with email and password_hash fields",
    context="""
    TASK FROM PLAN:
    - Create: src/models/user.py
    - Add User class with email (str) and password_hash (str) fields
    - Use bcrypt for password hashing
    - Include __repr__ for debugging

    FOLLOW TDD:
    1. Write failing test in tests/models/test_user.py
    2. Run: pytest tests/models/test_user.py -v (verify FAIL)
    3. Write minimal implementation
    4. Run: pytest tests/models/test_user.py -v (verify PASS)
    5. Run: pytest tests/ -q (verify no regressions)
    6. Commit: git add -A && git commit -m "feat: add User model with password hashing"

    PROJECT CONTEXT:
    - Python 3.11, Flask app in src/app.py
    - Existing models in src/models/
    - Tests use pytest, run from project root
    - bcrypt already in requirements.txt
    """,
    toolsets=['terminal', 'file']
)

Read the full file on GitHub · 340 lines

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. 9d ago First seen · 340 lines · 32 tokens per session scan A ef66a4392fb8

Subscribe to this mod's changes

subagent-driven-development is a skill published in the GitHub repository moltis-org/moltis (2,851 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 2,212 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 81% identical to subagent-driven-development, differing in 31 lines, and is treated as a copy.