Yunus Kılıç
620a061a90
Adds Codex as a conversion/install target: each agent → `~/.codex/agents/<slug>.toml` with the three required Codex fields (name, description, developer_instructions). Validated: all 184 agents generate valid, parseable TOML (incl. 21k-char agents with embedded code blocks) via the PR's TOML basic-string escaper. Matches OpenAI's documented custom-agent schema. Thanks @yunuskilicdev.
Codex Integration
Converts all Agency agents into Codex custom agent TOML files. Each source
agent becomes one standalone .toml file containing the minimal Codex-required
fields: name, description, and developer_instructions.
Installation
Prerequisites
- Codex installed
Convert And Install
# Generate integration files (required on fresh clone)
./scripts/convert.sh --tool codex
# Install agents
./scripts/install.sh --tool codex
This copies generated agent files to ~/.codex/agents/.
Generated Format
Each generated file lives in:
integrations/codex/agents/<slug>.toml
The mapping is intentionally minimal:
nameis copied from the source frontmatter unchangeddescriptionis copied from the source frontmatter unchangeddeveloper_instructionscontains the full Markdown body unchanged
Source-only metadata such as color, emoji, vibe, and other unsupported
frontmatter fields are omitted.
Usage
After installation, reference the custom agent by name in Codex:
Use the Frontend Developer agent to review this component.
Codex uses the name field inside the TOML file as the source of truth, so the
generated filename slug is only for filesystem safety.
Regenerate
After modifying source agents:
./scripts/convert.sh --tool codex
./scripts/install.sh --tool codex
Troubleshooting
Codex integration not found
Generate the Codex artifacts before installing:
./scripts/convert.sh --tool codex
Codex not detected
Make sure codex is in your PATH, or that ~/.codex/ already exists:
which codex
codex --help