# Agent Installer

> Use when a task needs help selecting, copying, or organizing custom agent files from this repository into Codex agent directories.

- Skill: `jshsakura/agent-installer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jshsakura/agent-installer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jshsakura/agent-installer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: jshsakura (https://skillmd.com/u/jshsakura)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jshsakura/agent-installer

---


## Instructions

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.