Codex · softaworks — Claude Code skill: code analysis and refactoring
A skill that runs Codex CLI for code analysis, refactoring, and automated editing. Uses GPT-5.2 by default with adaptive reasoning, hitting 76.3% on SWE-bench.
npx skills add softaworks/agent-toolkit --skill codex -a claude-codeWhat codex does
Codex brings GPT-5.2 into your editor: you describe a task, the skill invokes codex exec with the right reasoning level (xhigh, high, medium, low) and sandbox mode (read-only, workspace-write, or danger-full-access). Under the hood — CLI v0.57.0+ that manages the model, analysis depth, and filesystem access.
Workflow is straightforward: the skill asks for reasoning level and sandbox mode, then runs the command with flags like -m, --config model_reasoning_effort, --sandbox, --skip-git-repo-check and suppresses stderr (thinking tokens) by default. After execution, it offers to resume the session via codex resume --last to refine or expand the analysis without a restart.
GPT-5.2 is cheaper and faster than GPT-5.1 (30% savings on standard tasks), and cached input gets a 90% discount, valid for up to 24 hours. For harder cases, gpt-5.2-max provides 128K output, and gpt-5.2-mini quadruples your allowance. Requires Codex CLI v0.57.0 or newer.
What it helps with
- analyze code and find bugs
- refactor functions and architecture
- apply automated fixes to files
- optimize code performance
- check security and best practices
Example prompts for the agent
- Analyze my
index.tsfor production-readiness issues, use high reasoning - Refactor the entire User class for readability, workspace-write mode
- codex resume — continue the analysis and suggest SQL query optimization
How to install codex
1Skills CLI (Vercel)
npx skills add softaworks/agent-toolkit --skill codex -a claude-code2Manually: put the files in place
~/.claude/skills/codex/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/codex/
1Skills CLI (Vercel)
npx skills add softaworks/agent-toolkit --skill codex -a codex2Manually: put the files in place
.agents/skills/codex/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add softaworks/agent-toolkit --skill codex -a cursor2Manually: put the files in place
.cursor/skills/codex/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install softaworks/agent-toolkit codex2Manually: put the files in place
.github/skills/codex/SKILL.md1Skills CLI (Vercel)
npx skills add softaworks/agent-toolkit --skill codex -a gemini-cli2Platform CLI
gemini skills install https://github.com/softaworks/agent-toolkit --path skills/codexManually: put the files in place
.devin/skills/codex/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add softaworks/agent-toolkit --skill codex -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about codex
How do I install Codex in Claude Code?
Run npx skills add softaworks/agent-toolkit --skill codex -a claude-code, then open ~/.claude/skills/codex/SKILL.md to verify. On other platforms the command differs: for Codex use npx skills add softaworks/agent-toolkit --skill codex -a codex, for Cursor use npx skills add softaworks/agent-toolkit --skill codex -a cursor.
What is reasoning effort and which should I pick?
It controls analysis depth: xhigh for very complex tasks (architecture, deep bugs), high for refactoring and security, medium for standard changes, low for simple edits. The skill will ask before running.
Can I continue a session after the first analysis?
Yes, use codex resume or say 'codex resume' — the skill restores the model, reasoning effort, and sandbox mode from the prior run and waits for your next task.
Source text
SKILL.md · MIT
--- 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 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` (no flags allowed) | | Run from another directory | Match task needs | `-C <DIR>` plus other flags `2>/dev/null` | ## Model Options | Model | Best for | Context window | Key features | | --- | --- | --- | --- | | `gpt-5.2-max` | **Max model**: Ultra-complex reasoning, deep problem analysis | 400K input / 128K output | 76.3% SWE-bench, adaptive reasoning, $1.25/$10.00 | | `gpt-5.2` ⭐ | **Flagship model**: Software engineering, agentic coding workflows | 400K input / 128K output | 76.3% SWE-bench, adaptive reasoning, $1.25/$10.00 | | `gpt-5.2-mini` | Cost-efficient coding (4x more usage allowance) | 400K input / 128K output | Near SOTA performance, $0.25/$2.00 | | `gpt-5.1-thinking` | Ultra-complex reasoning, deep problem analysis | 400K input / 128K output | Adaptive thinking depth, runs 2x slower on hardest tasks | **GPT-5.2 Advantages**: 76.3% SWE-bench (vs 72.8% GPT-5), 30% faster on average tasks, better tool handling, reduced hallucinations, improved code quality. Knowledge cutoff: September 30, 2024. **Reasoning Effort Levels**: - `xhigh` - Ultra-complex tasks (deep problem analysis, complex reasoning, deep understanding of the problem) - `high` - Complex tasks (refactoring, architecture, security analysis, performance optimization) - `medium` - Standard tasks (refactoring, code organization, feature additions, bug fixes) - `low` - Simple tasks (quick fixes, simple changes, code formatting, documentation) **Cached Input Discount**: 90% off ($0.125/M tokens) for repeated context, cache lasts up to 24 hours. ## Following Up - After every `codex` command, immediately use `AskUserQuestion` to confirm next steps, collect clarifications, or decide whether to resume with `codex exec resume --last`. - When resuming, pipe the new prompt via stdin: `echo "new prompt" | codex exec resume --last 2>/dev/null`. The resumed session automatically uses the same model, reasoning effort, and sandbox mode from the original session. - Restate the chosen model, reasoning effort, and sandbox mode when proposing follow-up actions. ## Error Handling - Stop and report failures whenever `codex --version` or a `codex exec` command exits non-zero; request direction before retrying. - Before you use high-impact flags (`--full-auto`, `--sandbox danger-full-access`, `--skip-git-repo-check`) ask the user for permission using AskUserQuestion unless it was already given. - When output includes warnings or partial results, summarize them and ask how to adjust using `AskUserQuestion`. ## CLI Version Requires Codex CLI v0.57.0 or later for GPT-5.2 model support. The CLI defaults to `gpt-5.2` on macOS/Linux and `gpt-5.2` on Windows. Check version: `codex --version` Use `/model` slash command within a Codex session to switch models, or configure default in `~/.codex/config.toml`.
© softaworks · MIT · softaworks/agent-toolkit
Similar skills
Everything for Code review and refactoring →codex by other authors comes first.