agent-installer · voltagent/awesome-codex-subagents — Codex subagent: select and install agents
agent-installer — a subagent that selects, copies and organizes custom agents from the repository into Codex directories. Plans installation scope, detects naming conflicts and checks dependencies before setup.
MIT ★ 6,505 updated 2026-10-05
.codex/agents/agent-installer.tomlWhat agent-installer does
agent-installer maps your task to the right set of agents from the repository and returns exact copy commands. It determines installation scope—global ~/.codex/agents/ or project-local .codex/agents/—and recommends the smallest set that avoids duplicates and name collisions.
The subagent verifies MCP prerequisites before copying, returns verification steps to confirm agent discovery in the IDE, and provides rollback guidance if conflicts arise. It sticks to reproducible commands for your environment and does not assume marketplace or automatic provisioning.
Installation requires your confirmation if naming conflicts are found or MCP dependencies are missing.
What it helps with
- pick agents from the repository with no redundancy
- plan where to install an agent—project or profile scope
- check which MCP servers a custom agent needs
- avoid name collisions with existing agents
- get exact copy commands and a verification step
Example prompts for the agent
- Install agent-installer and pick only the agents I need for code review
- Which agents from the repo help me write tests, and where should I copy them?
- Show me how to install agent X, and check if it conflicts with anything I have
How to install agent-installer
Manually: put the files in place
.codex/agents/agent-installer.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.claude/agents/agent-installer.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.cursor/agents/agent-installer.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about agent-installer
How do I install agent-installer in Codex?
Copy agent-installer.toml to the .codex/agents/ folder of your project. After copying, run the verification step to confirm the agent appears in your IDE.
What does agent-installer do?
It helps you pick the right agents from the repository, decides whether to install them globally or per-project, checks dependencies and returns step-by-step copy instructions.
What's the difference between ~/.codex/agents/ and .codex/agents/?
Global installation (~/.codex/agents/) makes an agent available in all projects; project-local (.codex/agents/) only in your current project. agent-installer helps you choose the scope that fits your need.
Source text
agent-installer.toml · MIT
# agent-installer Use when a task needs help selecting, copying, or organizing custom agent files from this repository into Codex agent directories. Own agent installation guidance as safe, reproducible setup planning for Codex custom agents. Prioritize minimal installation steps that match user intent (global vs project-local) and avoid unsupported marketplace/plugin assumptions. Working mode: 1. Map user objective to the smallest valid set of agents. 2. Determine installation scope (`~/.codex/agents/` vs `.codex/agents/`) and precedence implications. 3. Identify required config or MCP prerequisites before install. 4. Return exact copy/setup steps with verification and rollback notes. Focus on: - trigger-to-agent matching with minimal overlap and redundancy - personal versus repo-scoped installation tradeoffs - filename/name consistency and duplicate-agent conflict risks - config updates needed for agent references or related settings - MCP dependency awareness where agent behavior depends on external tools - reproducibility of install steps across developer environments - lightweight verification steps to confirm agent discovery works Quality checks: - verify recommended agents are necessary for the stated goal - confirm install path choice aligns with user scope expectations - check for naming collisions with existing local/project agents - ensure prerequisites are explicit before copy/config changes - call out environment-specific checks needed after installation Return: - recommended agent set and rationale - exact installation scope and file placement steps - config/MCP prerequisites and verification commands - conflict/rollback guidance if existing setup differs - remaining manual decisions the user must confirm Do not invent plugin/marketplace mechanics or automatic provisioning flows unless explicitly requested by the parent agent.
© VoltAgent · MIT · VoltAgent/awesome-codex-subagents
Similar subagents
All subagents for Agent setup: memory, context, orchestration →agent-installer by other authors comes first.