AI SummaryA skill that enables integration with OpenAI Codex CLI for automated code analysis, refactoring, and editing tasks. Useful for developers who have Codex CLI installed and want AI-powered code manipulation capabilities.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "codex" skill in my project. Please run this command in my terminal: # Install skill into the correct directory mkdir -p .claude/skills/codex && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/codex/SKILL.md "https://raw.githubusercontent.com/ethanolivertroy/ets-agent-skills/main/codex/SKILL.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
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
Codex Skill Guide
This skill enables the use of Codex CLI for code analysis, refactoring, and automated editing tasks.
When to Use This Skill
Use this skill when the user: • Asks to run Codex CLI commands (codex exec, codex resume) • References OpenAI Codex for code analysis • Needs automated code refactoring • Wants AI-powered code editing
Running a Task
• Ask the user (via AskUserQuestion) which model to run (gpt-5.2-codex or gpt-5.2) AND which reasoning effort to use (xhigh, high, medium, or low) in a single prompt with two questions. • Select the sandbox mode required for the task; default to --sandbox read-only unless edits or network access are necessary. • Assemble the command with the appropriate options: • -m, --model <MODEL> • --config model_reasoning_effort="<xhigh|high|medium|low>" • --sandbox <read-only|workspace-write|danger-full-access> • --full-auto • -C, --cd <DIR> • --skip-git-repo-check • Always use --skip-git-repo-check. • When continuing a previous session: • Use codex exec --skip-git-repo-check resume --last via stdin • Don't use any configuration flags unless explicitly requested by the user (e.g., if they specify the model or reasoning effort when requesting to resume) • Resume syntax: echo "your prompt here" | codex exec --skip-git-repo-check resume --last 2>/dev/null • All flags must be inserted between exec and resume • 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. • Run the command, capture stdout/stderr (filtered as appropriate), and summarize the outcome for the user. • After Codex completes, inform the user: "You can resume this Codex session at any time by saying 'codex resume' or asking me to continue with additional analysis or changes."
Quick Reference
| Use case | Sandbox mode | Key flags | | --- | --- | --- | | Read-only review or analysis | read-only | --sandbox read-only 2>/dev/null | | Apply local edits | workspace-write | --sandbox workspace-write --full-auto 2>/dev/null | | Permit network or broad access | danger-full-access | --sandbox danger-full-access --full-auto 2>/dev/null | | Resume recent session | Inherited from original | echo "prompt" \\| codex exec --skip-git-repo-check resume --last 2>/dev/null | | Run from another directory | Match task needs | -C <DIR> plus other flags 2>/dev/null |
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster