
Sub Agents
- 514 installs
- 3.9k repo stars
- Updated January 26, 2026
- parcadei/continuous-claude-v3
sub-agents is a Claude Code reference skill for creating isolated sub-agents with custom prompts, tool lists, and models for developers who need specialized parallel agents for review, debugging, or implementation tasks.
About
sub-agents is a build-phase agent-tooling skill documenting Claude Code sub-agent creation and management. Developers use `/agents` for interactive setup or hand-author YAML-front-matter files in `.claude/agents/` with `name`, `description`, optional `tools`, and `model` fields (`sonnet`, `haiku`, `claude-opus-4-5-20251101`, `inherit`). Built-in agents include General-purpose (Sonnet, all tools), Plan (Sonnet, read-only), and Explore (Haiku, read-only). Examples cover code-reviewer, debugger, and implementer tool sets, plus resumable sessions via `claude -r "agentId"` and agent chaining patterns. Project agents in `.claude/agents/` override user agents in `~/.claude/agents/`. Allowed tools on the skill itself are Read, Write, and Bash. Developers reach for sub-agents when decomposing large coding tasks into scoped agents with least-privilege tool access and model-appropriate cost/latency tradeoffs.
- Spawns purpose-built sub-agents that run in parallel with distinct roles and prompts
- Coordinates hand-offs, context sharing, and synthesis between agents
- Reduces token usage and context bloat by delegating narrow scopes
- Works with Claude Code, Cursor, and compatible agent hosts
- Enables continuous, multi-threaded agent workflows without manual orchestration
Sub Agents by the numbers
- 514 all-time installs (skills.sh)
- +2 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #1,746 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/parcadei/continuous-claude-v3 --skill sub-agentsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 514 |
|---|---|
| repo stars | ★ 3.9k |
| Last updated | January 26, 2026 |
| Repository | parcadei/continuous-claude-v3 ↗ |
How do you create Claude Code sub-agents?
Let Claude autonomously spawn, coordinate, and manage specialized sub-agents that each handle distinct parts of a complex coding task.
Who is it for?
Claude Code developers orchestrating specialized agents for review, exploration, debugging, or implementation with isolated contexts.
Skip if: Cursor or Codex users without Claude Code `.claude/agents/` support who need IDE-native agent configuration instead.
When should I use this skill?
User asks how to create a sub-agent, configure agent tools, select agent models, chain agents, or use `/agents` in Claude Code.
What you get
`.claude/agents/*.md` agent definitions with descriptions, tool allowlists, model picks, and runnable `/agents` or CLI configurations.
- Agent markdown files
- Tool-restricted agent configs
- Agent chaining recipes
By the numbers
- Documents 3 built-in Claude Code agents: General-purpose, Plan, Explore
- Shows 3 example role tool bundles: reviewer, debugger, implementer
- Supports 4 model options: sonnet, haiku, claude-opus-4-5-20251101, inherit
Files
Sub-Agents Reference
Create specialized AI agents with isolated contexts for specific tasks.
When to Use
- "How do I create a sub-agent?"
- "Configure agent tools"
- "What built-in agents exist?"
- "Agent model selection"
- "Agent chaining patterns"
Quick Start
Interactive (Recommended)
/agentsOpens menu to create, edit, and manage agents.
Manual Creation
mkdir -p .claude/agents
cat > .claude/agents/reviewer.md << 'EOF'
---
name: reviewer
description: Code review specialist. Use proactively after code changes.
tools: Read, Grep, Glob, Bash
model: sonnet
---
You are a senior code reviewer focusing on quality and security.
## Review Checklist
- Code clarity and naming
- Error handling
- Security vulnerabilities
- Test coverage
EOFCLI-Based
claude --agents '{
"reviewer": {
"description": "Code reviewer",
"prompt": "Review for quality and security",
"tools": ["Read", "Bash"],
"model": "sonnet"
}
}'Agent File Format
---
name: agent-name
description: When/why to use this agent
tools: Read, Edit, Bash # Optional, inherits all if omitted
model: sonnet # sonnet, haiku, claude-opus-4-5-20251101, inherit
---
System prompt content here...Configuration Fields
| Field | Required | Options |
|---|---|---|
name | Yes | lowercase, hyphens |
description | Yes | When to use |
tools | No | Tool list (inherits all if omitted) |
model | No | sonnet, haiku, claude-opus-4-5-20251101, inherit |
Built-In Agents
| Agent | Model | Tools | Purpose |
|---|---|---|---|
| General-purpose | Sonnet | All | Complex multi-step tasks |
| Plan | Sonnet | Read-only | Plan mode research |
| Explore | Haiku | Read-only | Fast codebase search |
Model Selection
| Model | Speed | Best For |
|---|---|---|
| Haiku | Fastest | Search, quick lookups |
| Sonnet | Fast | Most tasks (default) |
| Opus | Slower | Complex reasoning |
Tool Combinations
# Code Reviewer (read-only)
tools: Read, Grep, Glob, Bash
# Debugger
tools: Read, Edit, Bash, Grep, Glob
# Implementer
tools: Read, Write, Edit, Bash, GlobExample Agents
Code Reviewer
---
name: code-reviewer
description: Reviews code for quality and security. Use after code changes.
tools: Read, Grep, Glob, Bash
model: sonnet
---
Review code for:
- Security vulnerabilities
- Code quality issues
- Missing error handling
- Test coverage gaps
Output findings by priority: Critical > Warning > SuggestionDebugger
---
name: debugger
description: Debug errors and test failures.
tools: Read, Edit, Bash, Grep, Glob
model: inherit
---
Debugging process:
1. Capture error details
2. Identify failure location
3. Form hypotheses
4. Test and verify
5. Implement fixFile Locations
| Type | Location | Priority |
|---|---|---|
| Project | .claude/agents/ | Highest |
| User | ~/.claude/agents/ | Lower |
Advanced Patterns
Resumable Agents
[Agent returns agentId: "abc123"]
# Later: resume with context
claude -r "abc123" "Continue analysis"Agent Chaining
Use code-analyzer to find issues,
then use optimizer to fix themBest Practices
1. Single responsibility - One clear purpose per agent 2. Restrict tools - Only grant what's needed 3. Clear descriptions - Action-oriented, include "proactively" 4. Version control - Check .claude/agents/ into git
Related skills
FAQ
Where do sub-agents store project agents?
sub-agents stores project agents in `.claude/agents/*.md`, which overrides user-level agents in `~/.claude/agents/`. Each file uses YAML front matter for name, description, tools, and model.
Which built-in agents does sub-agents document?
sub-agents documents General-purpose (Sonnet, all tools), Plan (Sonnet, read-only), and Explore (Haiku, read-only) as Claude Code built-ins for complex tasks, planning, and fast search.
How does sub-agents recommend restricting tools?
sub-agents recommends least-privilege tool lists—e.g., reviewers get Read, Grep, Glob, Bash while implementers add Write and Edit—so agents cannot access capabilities outside their role.