Codex
- 119 installs
- 339 repo stars
- Updated August 4, 2026
- glebis/claude-skills
Run Codex-style iterative coding loops where the agent plans edits, applies patches, and re-verifies results across backend, frontend, and script tasks.
About
The codex skill from glebis/claude-skills emulates disciplined Codex-like agent coding inside Claude. It choreographs planning, targeted edits, and verification passes so complex changes land safely across services, scripts, and UI code while preserving context, testability, and review-friendly diffs.
- Structures plan-edit-test agent loops
- Encourages small verifiable diffs
- Integrates with repo context and commands
- Supports multi-file refactors
- Emphasizes regression checks after patches
Codex by the numbers
- 119 all-time installs (skills.sh)
- Ranked #3,867 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/glebis/claude-skills --skill codexAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 119 |
|---|---|
| repo stars | ★ 339 |
| Last updated | August 4, 2026 |
| Repository | glebis/claude-skills ↗ |
What it does
Run Codex-style iterative coding loops where the agent plans edits, applies patches, and re-verifies results across backend, frontend, and script tasks.
Files
Codex Skill Guide
Running a Task
1. Do NOT specify a model by default. The Codex CLI is configured with a ChatGPT account, and explicit model flags (-m gpt-5-codex, -m gpt-5, -m o4-mini) all fail with "not supported when using Codex with a ChatGPT account." Omitting -m lets Codex use its default model, which works. Only add -m if the user explicitly requests a specific model. 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:
--sandbox <read-only|workspace-write|danger-full-access>--full-auto-C, --cd <DIR>--skip-git-repo-check-m, --model <MODEL>(only if user explicitly requests)--config model_reasoning_effort="<high|medium|low>"(only if user explicitly requests)
4. Always use --skip-git-repo-check. 5. 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. 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. 6. 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. 7. Run the command, capture stdout/stderr (filtered as appropriate), and summarize the outcome for the user. 8. 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" \ |
| Run from another directory | Match task needs | -C <DIR> plus other flags 2>/dev/null |
Following Up
- After every
codexcommand, immediately useAskUserQuestionto confirm next steps, collect clarifications, or decide whether to resume withcodex 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 --versionor acodex execcommand 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.
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10