| name | codex-delegate |
| description | Delegate coding tasks to the OpenAI Codex CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility. |
| risk | safe |
| category | agent-orchestration |
| source | https://github.com/amElnagdy/delegate-skills |
| source_repo | amElnagdy/delegate-skills |
| source_type | community |
| date_added | 2026-08-26 |
| license | MIT |
| license_source | https://github.com/amElnagdy/delegate-skills/blob/master/LICENSE |
| compatibility | Requires the `codex` CLI (OpenAI Codex) installed and authenticated, Node 18+, and git. The orchestrating agent must be able to run shell commands and read files. Shell examples assume bash/zsh (macOS/Linux, or Git Bash/WSL on Windows). |
| metadata | {"version":"0.5.0"} |
Codex Delegate
When to Use
- You want to delegate a bounded coding task to a separate
codex implementer (OpenAI Codex) and then review its diff yourself.
- The user explicitly asked for delegation to this implementer.
You are the orchestrator. This skill lets you hand a bounded coding task to a separate
implementer — the OpenAI Codex CLI — then review what it produced and land it yourself. You write
the brief and own the judgment; Codex does the typing in its own sandbox; you verify and commit.
Nothing here is specific to one orchestrating agent. The loop needs only the ability to run a shell
command and read a file, so it works the same whether you are Claude Code, OpenCode with a selected
model, or any comparable agent. (It is designed for and run on Claude Code; treat other orchestrators
as designed-for, not yet proven.)
When NOT to use this
- The task is small enough to just do inline — delegation overhead is not worth it.
- The
codex CLI is not installed or not authenticated (run codex login).
- You want to write the code yourself, or you only need a review (use Codex's own
review command).
Prerequisites (check once)
codex --version succeeds. If not, install (npm i -g @openai/codex) and codex login.- Confirm which
codex is on PATH. Multiple installs are common (e.g. a current npm/nvm copy and
a stale Homebrew one). command -v codex shows the active one and codex --version its version —
an old binary predates flags this skill relies on (codex exec --json, -o, exec resume). The
relay also records the version it ran into result.json, so a stale binary is visible after the fact.
- You are in (or will point
--cd at) the target git repository.
The loop
Run these five steps per task. Steps 1, 4, and 5 are your judgment; 2 and 3 are mechanical.
1. Write the brief
Codex sees only the text you send — no repo memory, no chat history, no shared context. Everything the
task needs goes in the brief: the goal, the current state, what to change, what to leave untouched,
the project's actual gate commands (discover them from the repo's CLAUDE.md/AGENTS.md/Makefile —
do not assume), and a report contract. Tell Codex it will commit (you will). Keep one task per
brief. Full guidance and a template: .
