execute

A command that hands a specific coding plan or plan step to Codex, an AI coding agent, for implementation.

In plain words
What is it for?
Use it to implement a clearly defined change, either in the foreground for small work or in the background for longer tasks.
Why use it?
It separates planning from execution and lets Codex work from the original plan file when one exists.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/greenpolo/cc-multi-cli-plugin/execute
Clone the repo
git clone --depth 1 https://github.com/greenpolo/cc-multi-cli-plugin
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 552 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.00552
Opus 5 $0.00006 $0.00276
Sonnet 5 $0.00002 $0.00110
Haiku 4.5 $0.00001 $0.00055

Measured yesterday against content hash 6d0fe7387f21, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

execute scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/codex/commands/execute.md · 26 lines

What it actually says

Invoke the multi:codex-execute subagent via the Agent tool, forwarding the user's request as the prompt.

The subagent runs Codex in structured-execution mode — give it a concrete plan step, it implements it.

This is distinct from the official openai-codex plugin's /codex:rescue, which handles open-ended rescue. Use /codex:execute when you have a clear plan step; use /codex:rescue when Claude is stuck.

Raw user request: $ARGUMENTS

Execution:

  • Plan-by-reference (preferred when applicable): if a plan file is in conversation context (Plan mode Plan File Info block, a path like ~/.claude/plans/*.md, or a plan you authored this session), pass --plan <path> instead of paraphrasing. The subagent translates --plan to --prompt-file and Codex reads the file's bytes directly. See the multi-plan-handoff skill for full detection rules. Trigger phrases like "execute it via codex", "delegate to codex", "send this plan to codex" all qualify.
  • For a small, clearly bounded step, invoke the subagent in the foreground (blocking).
  • For a long-running or high-effort step (or --until-done), invoke the subagent with the Agent tool's run_in_background: true: the subagent runs Codex to completion in the foreground, so the harness wakes you with a <task-notification> when it finishes, fails, or the inactivity watchdog kills a hang — instead of stalling silently. Do NOT add the companion's --background flag for this (it detaches a worker the harness can't see); keep --background as an explicit fire-and-forget opt-in polled via /multi:status.
  • Preserve --model and --effort flags for the forwarded command — the subagent reads them.
  • If the user passes --resume, the subagent will continue the latest Codex execute thread for this repo.
  • If the request includes no prompt text AND no plan file in context, ask what Codex should implement before proceeding.

Return Codex's output verbatim.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 26 lines · 12 tokens per session scan A 6d0fe7387f21

Subscribe to this mod's changes

execute is a command published in the GitHub repository greenpolo/cc-multi-cli-plugin (89 stars, last pushed 16d ago), licensed Apache-2.0. It adds 12 tokens to every session and 552 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.