Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →amelnagdy/codex-delegate
Delegate a coding task to the OpenAI Codex CLI as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Codex — phrasings like "have Codex do X", "delegate this to Codex", "run it through Codex", or "use Codex to implement/fix/refactor" — or to run a queue of coding tasks through Codex while staying the reviewer. Prefer it over a one-shot Codex forwarder (such as the codex-rescue agent) when the user will review the d
Passed 14 of 20 test cases with the skill, and 3 of 20 without it.
and 14 more in the full report
13 fixed3 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/20/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
Which field in result.json contains Codex's full self-report text for orchestrator extraction?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies finalMessage as the field in result.json holding Codex's full report. | Missed | Passed |
The instructions your model reads when the skill loads.
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.)
codex CLI is not installed or not authenticated (run codex login).review command).codex --version succeeds. If not, install (npm i -g @openai/codex) and codex login.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.--cd at) the target git repository.Run these five steps per task. Steps 1, 4, and 5 are your judgment; 2 and 3 are mechanical.
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 not commit (you will). Keep one task per brief. Full guidance and a template: references/writing-the-brief.md.
This skill selects Codex as the implementer. Codex as the orchestrator is a separate role: background waiting requires codex-background and its configured MCP server. Installing
test cases passed, vs 3 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.