---

name: claude-subagent-roster description: Turn a single overloaded Claude agent into a routed team of specialized Sonnet-tier sub-agents supervised by an Opus-tier planner. Use when working on claude sub-agent roster designer.

Claude Sub-Agent Roster Designer

When one agent has to research, write, monitor, and reply, it thrashes and burns tokens. This skill helps you name the jobs, spin up a sub-agent per job with the right model tier, and write the delegation prompt so the main agent hands off cleanly. Result: parallel execution, lower spend, and clearer logs. Use once your solo agent starts hitting rate limits or context bloat.

What you get

• Sub-agent naming convention
• Per-role model recommendation (planner vs worker)
• Skill assignment matrix
• Delegation prompt template
• Cost-tracking checklist
• Handoff verification tests

Customize your output

• Number of sub-agents: 2, 3, 5, 7
• Recurring jobs to split off: research, drafting, monitoring, bookkeeping, custom
• Planner model: Opus, Fable 5
• Worker model: Sonnet, Haiku
• Per-agent skill grants: default, custom
• Handoff style: async, synchronous

Example output

'Created 3 sub-agents: Echo (Sonnet, social listening), Forge (Sonnet, drafting), Ledger (Sonnet, bookkeeping). Main agent Atlas (Opus) routes brand mention report to Echo then Forge in parallel. Est. monthly spend reduction 55 percent.'

Best for

Anyone already running a single Claude/OpenClaude agent hitting rate limits, context bloat, or bills that are too high.

---

Note: High confidence. Under-documented pattern with a big cost-and-quality upside.

Source: OpenClaude on Hostinger (unnamed) · https://www.youtube.com/watch?v=iSLruYDGT58 Category: AI Systems · Priority: P4