Codex route
The upstream Codex integration converts each source agent into a TOML custom agent with name, description, and developer instructions.
codex custom agents toml
Install fewer Codex agents first, with a plan for who handles what.
Plan which Agency Agents should become Codex custom agents and how to route tasks before installing the full roster.
233 agent files scanned
16 divisions
14 tool routes
Product-led answer
This page is built for the search intent around codex custom agents toml. It explains the task, shows the planner workflow, names limits, and routes full use through this domain's pricing path.
Planning value
The planner helps decide a small initial set before installing a broad roster into a user or project scope.
Evidence gate
Track which agent owns implementation, review, browser proof, and final production readiness.
Content utility gate
| Gate | Status |
|---|---|
| Target user and task | Teams choosing specialist agents for a concrete project, sprint, launch, or review. |
| Inputs and outputs | Planner input fields, sample roster output, risks, phase gates, and pricing route. |
| Limit | Preview only until payment; no official affiliation and no automatic install. |
| Extra value beyond generic SERP pages | Connects roster selection to NEXUS phases, evidence gates, and paid export instead of only listing prompts. |