
Codex
Invoke OpenAI Codex CLI (`codex exec` and session resumes) from Claude Code for analysis, refactor, and edit passes on your repo.
Overview
codex is an agent skill for the Build phase that connects Claude Code to the Codex CLI for exec and resumed coding sessions.
Install
npx skills add https://github.com/softaworks/agent-toolkit --skill codexWhat is this skill?
- Runs `codex exec` and supports Codex session resume from Claude Code
- Prompts for model choice (`gpt-5` or `gpt-5-codex`) when not specified
- Defaults to suppressing Codex thinking tokens via `2>/dev/null` to save context
- Documents clone-into-`~/.claude/skills/codex` installation path
- Requires `codex` on PATH and a working `codex --version` check
Adoption & trust: 3.7k installs on skills.sh; 2k GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want Codex’s analysis and edits on your repo but only work inside Claude Code and do not want manual terminal context switching.
Who is it for?
Solo builders already using Claude Code who have Codex CLI credentials and want orchestrated cross-model repo work.
Skip if: Anyone without the `codex` binary configured, or teams that need a managed cloud IDE instead of local CLI orchestration.
When should I use this skill?
User asks Claude Code to use Codex, run codex exec, or analyze/refactor the repo with the Codex CLI.
What do I get? / Deliverables
Claude invokes Codex with your chosen model and reasoning settings, returns actionable results, and keeps context lean unless you opt in to thinking-token output.
- Codex analysis or edit results surfaced in Claude Code
- Optional resumed Codex session output
Recommended Skills
Journey fit
Build is the primary phase because the skill wires a second model CLI into your local dev and agent workflow—not distribution or production ops. agent-tooling fits orchestrating Codex alongside Claude Code with model and reasoning-mode choices.
How it compares
Agent-to-CLI bridge skill—not an MCP server and not a replacement for staying entirely inside one model’s chat.
Common Questions / FAQ
Who is codex for?
Claude Code users with Codex CLI installed who want the primary agent to delegate analysis and edits to Codex automatically.
When should I use codex?
Use it during Build when refactoring modules, reviewing a Claude skill repo, or running a second model pass before you commit or open a PR.
Is codex safe to install?
Check Prism’s Security Audits panel, verify the skill-codex repo source, and limit shell/network permissions because the skill runs external CLI commands with your Codex credentials.
SKILL.md
READMESKILL.md - Codex
Leave a star ⭐ if you like it 😘 # Codex Integration for Claude Code <img width="2288" height="808" alt="skillcodex" src="https://github.com/user-attachments/assets/85336a9f-4680-479e-b3fe-d6a68cadc051" /> ## Purpose Enable Claude Code to invoke the Codex CLI (`codex exec` and session resumes) for automated code analysis, refactoring, and editing workflows. ## Prerequisites - `codex` CLI installed and available on `PATH`. - Codex configured with valid credentials and settings. - Confirm the installation by running `codex --version`; resolve any errors before using the skill. ## Installation Download this repo and store the skill in ~/.claude/skills/codex ``` git clone --depth 1 git@github.com:skills-directory/skill-codex.git /tmp/skills-temp && \ mkdir -p ~/.claude/skills && \ cp -r /tmp/skills-temp/ ~/.claude/skills/codex && \ rm -rf /tmp/skills-temp ``` ## Usage ### Important: Thinking Tokens By default, this skill suppresses thinking tokens (stderr output) using `2>/dev/null` to avoid bloating Claude Code's context window. If you want to see the thinking tokens for debugging or insight into Codex's reasoning process, explicitly ask Claude to show them. ### Example Workflow **User prompt:** ``` Use codex to analyze this repository and suggest improvements for my claude code skill. ``` **Claude Code response:** Claude will activate the Codex skill and: 1. Ask which model to use (`gpt-5` or `gpt-5-codex`) unless already specified in your prompt. 2. Ask which reasoning effort level (`low`, `medium`, or `high`) unless already specified in your prompt. 3. Select appropriate sandbox mode (defaults to `read-only` for analysis) 4. Run a command like: ```bash codex exec -m gpt-5-codex \ --config model_reasoning_effort="high" \ --sandbox read-only \ --full-auto \ --skip-git-repo-check \ "Analyze this Claude Code skill repository comprehensively..." 2>/dev/null ``` **Result:** Claude will summarize the Codex analysis output, highlighting key suggestions and asking if you'd like to continue with follow-up actions. ### Detailed Instructions See `SKILL.md` for complete operational instructions, CLI options, and workflow guidance. --- name: codex description: Use when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing. Uses GPT-5.2 by default for state-of-the-art software engineering. --- # Codex Skill Guide ## Running a Task 1. Default to `gpt-5.2` model. Ask the user (via `AskUserQuestion`) which reasoning effort to use (`xhigh`,`high`, `medium`, or `low`). User can override model if needed (see Model Options below). 2. Select the sandbox mode required for the task; default to `--sandbox read-only` unless edits or network access are necessary. 3. Assemble the command with the appropriate options: - `-m, --model <MODEL>` - `--config model_reasoning_effort="<high|medium|low>"` - `--sandbox <read-only|workspace-write|danger-full-access>` - `--full-auto` - `-C, --cd <DIR>` - `--skip-git-repo-check` 3. Always use --skip-git-repo-check. 4. When continuing a previous session, use `codex exec --skip-git-repo-check resume --last` via stdin. When resuming don't use any configuration flags unless explicitly requested by the user e.g. if he species the model or the reasoning effort when requesting to resume a session. Resume syntax: `echo "your prompt here" | codex exec --skip-git-repo-check resume --last 2>/dev/null`. All flags have to be inserted between exec and resume. 5. **IMPORTANT**: By default, append `2>/dev/null` to all `codex exec` commands to suppress thinking tokens (stderr). Only show stderr if the user explicitly requests to see thinking tokens or if debugging is needed. 6. Run the command, capture stdout/stderr (filtered as appropriate), and summarize the outcome for the user. 7. **After Codex completes**, inform the user: "You can resume this Codex session at any time by saying 'codex resume' or askin