codex-crewlisted
Install: claude install-skill lklimek/claudius
# Codex Crew — Enlisting Codex Agents
Codex agents (OpenAI Codex CLI, run via the `codex` plugin's `codex-companion.mjs` runtime) are external crew a coordinator can enlist alongside the claudius roster. Opt-in. Read once before the session's first Codex dispatch.
**Dispatch directly, never through `codex:codex-rescue`.** For coordinator-orchestrated work that subagent is pure overhead: one `Bash` call forwarding stdout unchanged — no monitoring, no analysis, unreliable lifecycle signals (`idle_notification`, teammate shutdown, stall tracking) layered over a worker that is already a detached Node process with its own job-state files — and it never exposes `--cwd`/`--prompt-file`, the root cause of most bugs below. Call `codex-companion.mjs task` directly (§ Direct Dispatch): nothing to spawn, track, or shut down. Reserve `codex:codex-rescue` for the user-typed `/codex:rescue` interactive command, which this skill doesn't govern.
## When to Enlist Codex
- **Opt-in, not default** — when the user asks, or per the coding preference below.
- **Coding-first (project default):** code-writing work prefers **Codex Sol** over Opus-tier claudius agents (`developer-bilby`) — an intentional override of `delegate`'s Token Economy tiering for implementation tasks.
- **Non-coding roles keep normal tiering:** review, QA, security, architecture, and docs stay with claudius agents unless the user opts them into Codex.
## Routing — One Model, High Effort
- **Codex Sol = `--model gpt-5.6-so