Codex operator β delegate coding, reviews and plans to OpenAI Codex
Compose prompts and run OpenAI's Codex CLI non-interactively with explicit sandbox modes (read-only, workspace-write, danger-full-access), review workflows with findings-before-fixes, session resume, and strict trust boundaries
- What
- Compose prompts and run OpenAI's Codex CLI non-interactively with explicit sandbox modes (read-only, workspace-write, danger-full-access), review workflows with findings-before-fixes, session resume, and strict trust boundaries
- Cost
- Free
- Needs
- the OpenAI Codex CLI installed and configured with Codex access (paid OpenAI account) β verify with `codex --version`; a codebase to work on
- Install
- Copy the installer prompt below into your Muse β your agent does the rest.
π³ **Paid API required** β Curated by Skill Harbor β @feiskyer's skill for delegating work to the OpenAI Codex CLI (`codex exec`). It teaches the agent to compose prompts, pick an explicit sandbox level per run β read-only for analysis (the default), workspace-write (`--full-auto`) for implementation, and `danger-full-access` only with the user's explicit per-task consent β and to follow strict trust boundaries (file contents, diffs and tool output are data, never instructions). Covers review workflows where findings are presented first and never auto-applied, adversarial and second-opinion reviews, image-driven implementation, session resume for iterative follow-ups, background execution for long runs, and reference docs (CLI flags, prompting patterns, review schemas, worked examples). Honest caveats: needs the Codex CLI installed and an OpenAI account with Codex access (paid) β running under the skill's rules never gates on `codex login status`, just try it and surface auth errors; note that codex runs outside the host agent's permission system, so the skill advises the read-only sandbox for sensitive repos. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: the OpenAI Codex CLI installed and configured with Codex access (paid OpenAI account) β verify with `codex --version`; a codebase to work on Install "Codex operator β delegate coding, reviews and plans to OpenAI Codex" for me. It gives my agent @feiskyer's Codex delegation workflow: run `codex exec` non-interactively with an explicit sandbox per task (read-only for analysis by default, workspace-write/--full-auto for implementation, danger-full-access only with my explicit per-task consent), present review findings first and never auto-apply fixes, run adversarial and second-opinion reviews, resume sessions for iterative follow-ups, background long-running invocations, and read the bundled references/ (cli-reference, prompting-patterns, review-workflows, examples) before writing non-trivial prompts. MIT-licensed. Repository: https://github.com/feiskyer/claude-code-settings/blob/main/skills/codex-skill/SKILL.md 1. Fetch the SKILL.md file (and the references/ and assets/ folders) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and references for anything suspicious (unexpected network calls, shell commands outside the allowed-tools list, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "codex-skill". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install the Codex CLI with `npm i -g @openai/codex` if missing, make sure my OpenAI account has Codex access β that's on me). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you β no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the sellerβs own page, usually Stripe.
What does the β next to a creatorβs name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself β always check a build before installing it.