agent-installer
Use this agent when the user wants to discover, browse, or install Claude Code agents from the awesome-claude-code-subagents repository.
Tools
bash, webfetch, read, write, glob
Model & source
haiku
VoltAgent/awesome-claude-code-subagents
Install
Paste this once. It creates ~/.claude/agents/, adds Claude Code if it is missing, and writes the file at the reviewed commit.
{ command -v claude >/dev/null || curl -fsSL https://claude.ai/install.sh | bash; } && mkdir -p ~/.claude/agents && curl -fsSL "https://raw.githubusercontent.com/VoltAgent/awesome-claude-code-subagents/ed74d115b7fb7026a22a4f816a8e3250f425e3b4/categories/09-meta-orchestration/agent-installer.md" -o ~/.claude/agents/agent-installer.md && echo "agent installed: agent-installer"Windows (PowerShell):
New-Item -ItemType Directory -Force "$env:USERPROFILE\.claude\agents" | Out-Null; iwr "https://raw.githubusercontent.com/VoltAgent/awesome-claude-code-subagents/ed74d115b7fb7026a22a4f816a8e3250f425e3b4/categories/09-meta-orchestration/agent-installer.md" -OutFile "$env:USERPROFILE\.claude\agents\agent-installer.md"
Then run claude and ask for the task — the agent is picked by its description.
Source
categories/09-meta-orchestration/agent-installer.md in VoltAgent/awesome-claude-code-subagents, pinned at ed74d115b7fb, license MIT.
Checked for hidden characters, outbound commands and self-installing shells — not a security audit. The agent runs with the tools listed above.
More in Orchestration
agent-organizer Use when you need to break a complex task into subtasks, match each to the capabilities of available subagents
context-manager Use to organize the shared context and state that a multi-agent workflow keeps in files — deciding directory/f
error-coordinator Use when you need to mine error logs and agent output for recurring failure and cascade patterns, then documen
it-ops-orchestrator Use for orchestrating complex IT operations tasks that span multiple domains (PowerShell automation, .NET deve
knowledge-synthesizer Use when you need to mine recurring patterns from agent logs, session transcripts, and workflow history, then