← ClaudeAtlas

codex-clilisted

OpenAI Codex CLI orchestration through `bash.exec`. Use when the user explicitly wants to run Codex from shell, install or authenticate Codex CLI, choose a Codex/OpenAI model, or execute one-shot `codex exec` or `codex review` workflows against a repo.
afkbot-io/afkbotio · ★ 3 · AI & Automation · score 67
Install: claude install-skill afkbot-io/afkbotio
# codex-cli Use this skill when AFKBOT should drive the external OpenAI Codex CLI through `bash.exec`. ## Default mode - Prefer non-interactive commands: - `codex exec` for one-shot task execution - `codex review` for review-only flows - Use plain `codex` only if the user explicitly wants an interactive TUI or login flow. - Launch from the target repo root, or pass `-C <dir>` explicitly. ## What to pass Build each `bash.exec` command from these inputs: 1. target workspace: - `cwd` in the tool call - optional `-C <dir>` if Codex should operate from a different root 2. task prompt: - one quoted prompt argument for short tasks - stdin piping for long prompts 3. model: - `-m <model>` when the user requested one 4. execution controls: - `-s read-only|workspace-write|danger-full-access` - `--full-auto` for sandboxed low-friction execution - `--json` when AFKBOT needs structured events - `-o <file>` or `--output-schema <file>` for machine-readable final output ## Common commands ```bash codex --version codex login status codex exec -C . -m gpt-5.3-codex --json "Fix the failing tests and explain the root cause" codex review -C . printf '%s\n' "Summarize the architecture of this repo" | codex exec - ``` ## Installation Codex CLI can be installed in several supported ways: ```bash npm install -g @openai/codex brew install --cask codex ``` - GitHub Releases also publish standalone binaries for macOS and Linux. ## Authentication - Preferred for