Everyone's building armies of AI "specialists" inside Claude Code. Most of them never trigger, collide with each other, and quietly bloat the very context window they were supposed to protect. I built and stress-tested 100 subagents — official built-ins, the big community collections, and a pile of my own — to find the handful that genuinely earn their keep. Here are the 12 I actually delegate to, the ones I deleted, and the uncomfortable truth about what a subagent is really for.
Why I Went Down This Rabbit Hole
This is the third time I've done this to myself. First it was 100 Claude Skills. Then 100 MCP servers. Now: subagents. Together they're the three pillars of the Claude Code stack — Skills give an agent competence, MCP servers give it capability, and subagents give it delegation. I'd covered two. The trilogy demanded the third.
And subagents are where the hype is loudest right now. Open GitHub and you'll find collections with hundreds of them: VoltAgent's awesome-claude-code-subagents ships 154+ agents across 10 categories with 22.9k stars; wshobson's marketplace packs 194 agents, 158 skills, and 16 orchestrators into 37.5k stars. The pitch is intoxicating: assemble a team of AI specialists — a security-auditor, a react-specialist, a kubernetes-specialist, a quant-analyst — and let Claude Code dispatch the right expert for every task.
