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 diff and commit it themselves. DO NOT USE for tasks small enough to do inline, or when the user wants
npx skills add amElnagdy/delegate-skills --skill codex-delegate --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Codex Delegate 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) 1. `codex --version` succeeds. If not, install (`npm i -g @openai/codex`) and `codex login`. 2. **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` sho
- When NOT to use this
- Prerequisites (check once)
- The loop
- 1. Write the brief
- 2. Dispatch
- 3. Wait for completion
- 4. Review — do not trust the self-report
- 5. Land it
- Read-only second opinions
- Authorization model
- If you have the openai-codex plugin
- References
node "<skill-dir>/scripts/relay.mjs" --brief brief.txt --cd /path/to/repo read-only (review/diagnosis, no edits): add --read-only continue the exact Codex session: add --session <threadId> (from result.json; send only the delta brief) fallback when no thread id is available: add --resume-last hard time limit (watchdog): add --timeout 2h (default: off; implementation runs routinely need 1-2h) see all options: node .../relay.mjs --help
What does the codex-delegate skill do?
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 diff and commit it themselves. DO NOT USE for tasks small enough to do inline, or when the user wants
How do I install it?
Run `npx skills add amElnagdy/delegate-skills --skill codex-delegate --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From amElnagdy/delegate-skills, a repository with 684 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.