This walks you through the three main patterns for splitting work across multiple LLM instances: supervisor (centralized control), swarm (peer handoffs), and hierarchical (layered abstraction). The key insight is that you're doing this for context isolation, not role-playing organizational structure. Watch out for the "telephone game" problem where supervisors lose 50% performance by paraphrasing sub-agent responses instead of forwarding them directly. The token economics section is especially honest about costs, showing multi-agent systems can burn tokens much faster than single-agent approaches. Use it when you're actually hitting context limits or need true parallelization, not just because multiple agents sound more sophisticated.
npx -y skills add muratcankoylan/agent-skills-for-context-engineering --skill multi-agent-patterns --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
sickn33/antigravity-awesome-skills
moizibnyousaf/ai-agent-skills
github/awesome-copilot