agentleFS
legibetlegibet/agent-skills/skills/archive/codex-cli/SKILL.md

codex-cli

Skill0 starsChanged 26 days agoMITView on GitHub

Use Codex CLI as an independent agent for delegated work, code review, or continued discussion in an existing session.

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use opencode-cli, claude-cli and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • julweberSkill

    opencode-cli

    Expert control of opencode via the command line. Use when running opencode TUI, headless server, web UI, or the `run` non-interactive mode; managing sessions, providers, agents, MCP servers, models, stats, import/export, GitHub integration, debugging, database tools, upgrades, or shell completions.

    Also in 5 projects that use this

  • julweberSkill

    claude-cli

    Expert control of the `claude` CLI (Claude Code). Use when running Claude Code interactively or non-interactively, managing sessions, configuring MCP servers, managing plugins, handling authentication, or piping prompts through claude for scripting.

    Also in 3 projects that use this

  • ihiteshguptaSkill

    terraform

    Expert in Infrastructure as Code with Terraform. Use for creating, managing, and versioning infrastructure across cloud providers.

    Also in 3 projects that use this

  • mrgoonieSkill

    claude-code

    Also in 4 projects that use this

  • GoogleSkill

    ponytail

    Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

    Also in 4 projects that use this

  • MicrosoftSkill

    caveman

    Ultra-compressed response style that reduces output token count while preserving technical accuracy, with intensity levels and auto-clarity safety rules

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use gpt-6.1-sol with high reasoning effort by default:

    line 12
  2. Very specific:

    Use gpt-6.1-sol with high effort for most delegated tasks.

    line 35
  3. Very specific:

    Use codex exec --help, codex exec resume --help, and codex exec review --help for the command surface installed on the machine.

    line 76

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Codex CLI

Codex runs non-interactively through codex exec. A new run starts a separate Codex session in the selected working directory, streams progress to stderr, and prints its final response to stdout. Redirect stderr to /tmp/codex.err so the turn log stays out of the caller context. A run is done when the process exits; stdout is the reply. If the command fails, read /tmp/codex.err.

Run a task

Use gpt-6.1-sol with high reasoning effort by default:

codex -a never \
  -C <working-directory> \
  -m gpt-6.1-sol \
  -c model_reasoning_effort=high \
  exec --skip-git-repo-check "<request>" \
  </dev/null 2>/tmp/codex.err

-a never is a global flag and therefore appears before exec. It keeps an unattended run from waiting for interactive approval; failed operations return to Codex instead.

--skip-git-repo-check lifts Codex's trusted-directory check; without it an unattended run fails before doing any work.

</dev/null> keeps piped stdin from being appended to the prompt. For a long request, write it to a file and pass - < file in place of the quoted prompt and </dev/null — inline quoting breaks on quotes and newlines.

Model and reasoning

Available models, in ascending capability and cost: gpt-6-luna, gpt-6.1-sol. Set the model explicitly with -m on every run.

Reasoning effort accepts medium, high, xhigh, or max (not low). Higher effort gives the model more room to deliberate and generally increases latency. Set it explicitly with -c model_reasoning_effort=<level>.

Use gpt-6.1-sol with high effort for most delegated tasks. Use gpt-6-luna with xhigh or max for simple but tedious tasks to improve reliability at low cost.

Continue a session

resume --last continues the most recent session in that working directory. A thread ID continues a specific one. The thread id is on the session id: line in /tmp/codex.err. Keep model and effort unless the caller picks different values.

codex -a never \
  -C <working-directory> \
  -m gpt-6.1-sol \
  -c model_reasoning_effort=high \
  exec resume --skip-git-repo-check --last "<follow-up>" \
  </dev/null 2>/tmp/codex.err
codex -a never \
  -C <working-directory> \
  -m gpt-6.1-sol \
  -c model_reasoning_effort=high \
  exec resume --skip-git-repo-check <thread-id> "<follow-up>" \
  </dev/null 2>/tmp/codex.err

Review code

Pass either one scope flag or a prompt. --help lists both; the CLI still rejects that combination (exit 2).

codex -a never \
  -C <working-directory> \
  -m gpt-6.1-sol \
  -c model_reasoning_effort=high \
  exec review --skip-git-repo-check --uncommitted \
  </dev/null 2>/tmp/codex.err

Other shapes: review --base <branch>, review --commit <sha>, review "<instructions>".

Command reference

Use codex exec --help, codex exec resume --help, and codex exec review --help for the command surface installed on the machine.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.