How do I install the Codex CLI Agent skill?

Run npx skillmds@latest add iml1s/codex-cli-agent in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Codex CLI Agent safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Codex CLI Agent?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Codex CLI Agent free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Codex CLI Agent?

ImL1s (@iml1s) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Codex CLI Agent by iml1s — Agent Skill

Name: Codex CLI Agent
Author: ImL1s

Codex CLI Agent

Run OpenAI Codex CLI headlessly via codex-exec.sh (codex exec). Use when the user asks for Codex, GPT coding agent, codex exec, Codex subagents, or spawn_agents_on_csv. -r / read-only sandbox blocks workspace writes — use -s workspace-write when the prompt must write files. -T prefers subagents. Orchestrator owns git (--no-git).

ImL1s c02348a 5 files · 18.3 KB Updated Sep 17, 2026

File contents

Codex CLI (`codex exec`) Executor

When to use

User wants Codex / codex exec as the coding agent
Need Codex subagents, agent TOML profiles, or CSV fan-out
Sandboxed writes (-s workspace-write) vs strict read-only reviews (-r)

Wrapper

./codex-exec.sh -C /path/to/repo -s workspace-write "Implement X. NO git."
./codex-exec.sh -r -C /path/to/repo "Review for bugs"          # sandbox read-only
./codex-exec.sh -T -C /path/to/repo "Parallelize with subagents"
./codex-exec.sh -j -o /tmp/last.txt -f /tmp/bundle.txt
./codex-exec.sh --enable some_feature -m <model> "…"

Flags: -m · -t · -C · -s read-only|workspace-write|danger-full-access · -o last-message file · -f · -j/--json · -r · -T · --skip-git-repo-check (default on) · --require-git-repo · --ephemeral · --add-dir · --image · --enable · --profile · --no-git · -- passthrough.

-C is absolutized before use (avoids nested relative cwd).

Sandbox vs writing answer files

If the prompt must write a file under the workspace, do not use -r / read-only. That fails with writing is blocked by read-only sandbox after the model finishes reasoning. Use -s workspace-write and instruct “only write the designated path”, or capture stdout.

Native multi-agent

Subagents (parallel spawn + synthesize); custom roles in ~/.codex/agents/*.toml or .codex/agents/
Experimental batch: spawn_agents_on_csv (one worker per CSV row)
Feature flags: codex features list|enable|disable
-T asks Codex to prefer subagents / CSV fan-out when useful

Models

Do not hard-code a stale model table. Discover via your Codex build / account docs. Pin with -m when automation requires stability.

Discipline

Always --skip-git-repo-check outside git repos. Exit code untrusted. Orchestrator owns git.

---name: codex-cli-agentdescription: Run OpenAI Codex CLI headlessly via codex-exec.sh (codex exec). Use when the user asks for Codex, GPT coding agent, codex exec, Codex subagents, or spawn_agents_on_csv. -r / read-only sandbox blocks workspace writes — use -s workspace-write when the prompt must write files. -T prefers subagents. Orchestrator owns git (--no-git).---# Codex CLI (`codex exec`) Executor## When to use- User wants **Codex** / `codex exec` as the coding agent- Need Codex **subagents**, agent TOML profiles, or CSV fan-out- Sandboxed writes (`-s workspace-write`) vs strict read-only reviews (`-r`)## Wrapper```bash./codex-exec.sh -C /path/to/repo -s workspace-write "Implement X. NO git."./codex-exec.sh -r -C /path/to/repo "Review for bugs" # sandbox read-only./codex-exec.sh -T -C /path/to/repo "Parallelize with subagents"./codex-exec.sh -j -o /tmp/last.txt -f /tmp/bundle.txt./codex-exec.sh --enable some_feature -m <model> "…"```Flags: `-m` · `-t` · `-C` · `-s` read-only|workspace-write|danger-full-access · `-o` last-message file ·`-f` · `-j/--json` · `-r` · `-T` · `--skip-git-repo-check` (default on) · `--require-git-repo` ·`--ephemeral` · `--add-dir` · `--image` · `--enable` · `--profile` · `--no-git` · `--` passthrough.`-C` is absolutized before use (avoids nested relative cwd).## Sandbox vs writing answer filesIf the prompt must **write a file under the workspace**, do **not** use `-r` / `read-only`.That fails with `writing is blocked by read-only sandbox` after the model finishes reasoning.Use `-s workspace-write` and instruct “only write the designated path”, **or** capture stdout.## Native multi-agent- Subagents (parallel spawn + synthesize); custom roles in `~/.codex/agents/*.toml` or `.codex/agents/`- Experimental batch: `spawn_agents_on_csv` (one worker per CSV row)- Feature flags: `codex features list|enable|disable`- `-T` asks Codex to prefer subagents / CSV fan-out when useful## ModelsDo not hard-code a stale model table. Discover via your Codex build / account docs.Pin with `-m` when automation requires stability.## DisciplineAlways `--skip-git-repo-check` outside git repos. Exit code untrusted. Orchestrator owns git.

Frequently asked questions