codex-cli
The codex-cli subagent executes the Codex CLI command with a user's code analysis prompt, detecting the operating system to select the appropriate shell (zsh for macOS, bash for Linux, or PowerShell for Windows). Use this when you need GPT-5.2 perspective on code analysis through the Codex command-line interface.
mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/centminmod/my-claude-code-setup/HEAD/.claude/agents/codex-cli.md -o ~/.claude/agents/codex-cli.mdcodex-cli.md
# CLI Passthrough Agent Execute the Codex CLI command with the user's prompt. Use appropriate shell based on platform: ## Platform Detection First, detect the platform and choose the shell: - **macOS (darwin)**: Use `zsh -i -c` (if codex alias in ~/.zshrc) or direct `codex` command - **Linux**: Use `bash -i -c` (if codex alias in ~/.bashrc) or direct `codex` command - **Windows**: Use `powershell -Command` or direct `codex` command ## Execution (timeout: 120000ms) **Direct command (preferred if codex is in PATH):** ```bash codex -p readonly exec "USER_PROMPT" --json ``` **For macOS (if codex needs shell config):** ```bash zsh -i -c "codex -p readonly exec 'USER_PROMPT' --json" ``` **For Linux (if codex needs shell config):** ```bash bash -i -c "codex -p readonly exec 'USER_PROMPT' --json" ``` **For Windows (PowerShell):** ```powershell powershell -Command "codex -p readonly exec 'USER_PROMPT' --json" ``` Substitute USER_PROMPT with the input, execute, return only raw output.
Generate, edit-from-reference, or analyze images with AI via OpenRouter (gemini, geminipro, riverflow, flux2, seedream, gpt5, gpt5.4; Cloudflare AI Gateway BYOK). Also analyze a video (--analyze-video, read-only — no video generated) into a text description for video prompts. Use when the user asks to generate an image, create a PNG, make an icon, make it transparent, edit with a reference, design a logo/banner, describe/analyze/explain an image ("what's in this image"), or describe/analyze a video ("what happens in this video").
>
Consult official Claude Code documentation from code.claude.com using selective fetching. Use when working on hooks, skills, subagents, plugins, agent teams, MCP servers, permissions, settings, CI/CD (GitHub Actions, GitLab), IDE extensions (VS Code, JetBrains), desktop/web app features, scheduling, memory/CLAUDE.md, deployment (Bedrock, Vertex, Foundry), sandboxing, monitoring, or any Claude Code feature requiring official docs. Fetches only the specific docs needed per task.
Use for codebase analysis, forensic examination, and code mapping — locating functions, classes, and logic; security vulnerability analysis; pattern detection; architectural consistency checks; and navigable code references with exact file:line numbers. Delegate when the user needs to find where code lives, understand how a feature works, or trace a bug or vulnerability to its source.
Dual-AI code analysis pairing OpenAI Codex with Claude code-searcher — the lightest consult variant, two citation-verified perspectives. Use for a quick second opinion on a code question.
Dual-AI code analysis pairing z.ai GLM 5.2 with Claude code-searcher — a lightweight two-model second opinion. Use for a quick z.ai-backed check on a code question.
Execute TZ='Australia/Brisbane' date command and return ONLY the raw output. No formatting, headers, explanations, or parallel agents.
Use this agent proactively to synchronize memory bank documentation with actual codebase state, ensuring architectural patterns in memory files match implementation reality, updating technical decisions to reflect current code, aligning documentation with actual patterns, maintaining consistency between memory bank system and source code, and keeping all CLAUDE-*.md files accurately reflecting the current system state. Examples: <example>Context: Code has evolved beyond documentation. user: "Our code has changed significantly but memory bank files are outdated" assistant: "I'll use the memory-bank-synchronizer agent to synchronize documentation with current code reality" <commentary>Outdated memory bank files mislead future development and decision-making.</commentary></example> <example>Context: Patterns documented don't match implementation. user: "The patterns in CLAUDE-patterns.md don't match what we're actually doing" assistant: "Let me synchronize the memory bank with the memory-bank-synchronizer agent" <commentary>Memory bank accuracy is crucial for maintaining development velocity and quality.</commentary></example>