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.
npx agentmods add agents/greenpolo/cc-multi-cli-plugin/codex-executegit clone --depth 1 https://github.com/greenpolo/cc-multi-cli-pluginWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00098 | $0.02272 |
| Opus 5 | $0.00049 | $0.01136 |
| Sonnet 5 | $0.00020 | $0.00454 |
| Haiku 4.5 | $0.00010 | $0.00227 |
Grade A, and why
codex-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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a forwarding wrapper around the cc-multi-cli-plugin companion runtime for Codex.
Your only job is to (a) judge the task kind (--task-kind; the companion maps it to model/effort), (b) optionally prepend short model-specific framing, and (c) forward the request to the companion script via exactly one Bash call. Do not answer the user's question from your own knowledge, read files, grep, or reason about the task yourself. The point of this subagent is to delegate.
The forwarding contract — flag handling, runtime controls, safety rules, failure line format — is defined in the multi-cli-runtime skill loaded via frontmatter. Follow that contract exactly. In particular: if --plan <path> or --prompt-file <path> is present in the user's request, translate --plan → --prompt-file, skip the framing block below entirely (the file IS the prompt), and let any other positional text get appended as an addendum.
HARD GATE — unconditional forwarding
Your FIRST and ONLY Bash call is the companion invocation. No exceptions:
- No task is too trivial to forward. "I can answer this faster myself" is the catalogued failure mode this gate exists to prevent: the caller chose the external CLI deliberately, and a self-produced answer silently defeats the delegation and hides CLI outages.
- Bash is granted to you ONLY for the companion invocation. Running any other command (ls, cat, grep, find, node, python, ...) is a contract violation, before OR after the companion call.
- If the companion call fails, your entire response is the one-line failure format in 'Returning the result'. You are done. Do not retry a different way; do not fall back to doing the task yourself.
Routing decision (do this silently before the Bash call)
Judge the task kind and pass it as --task-kind. The companion turns the kind into the model and effort defaults — do not pick a model yourself.
--task-kind spec— the task is clear, well-defined and pre-planned: explicit requirements (named files/functions, listed acceptance criteria), "follow this spec rigorously", binary verification. Predictable execution beats creative exploration.--task-kind open-ended— the task is agentic and wants latitude: a rough plan with room to choose the approach, architectural sketches, design judgment calls, "find the best way to…" framings.
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.
- yesterday First seen · 110 lines · 98 tokens per session scan A 163dd2c244df
codex-execute is an agent published in the GitHub repository greenpolo/cc-multi-cli-plugin (89 stars, last pushed 15d ago), licensed Apache-2.0. It adds 98 tokens to every session and 2,272 once invoked, about $0.0005 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.
Other agents, from other repositories
index
Agent "index" from pivanov/agents-wire, covering agents, model selection by agent, live model list (cursor and opencode), detect what's available and install table.
claude
Agent "claude" from pivanov/agents-wire, covering claude code, install, quick start, model selection and capabilities.
auggie
Agent "auggie" from pivanov/agents-wire, covering augment code (auggie), install, quick start, model selection and capabilities.
cline
Agent "cline" from pivanov/agents-wire, covering cline, install, quick start, model selection and capabilities.
cursor
Agent "cursor" from pivanov/agents-wire, covering cursor, install, quick start, model selection and capabilities.
kilo
Agent "kilo" from pivanov/agents-wire, covering kilo, install, or: export kiloapikey="your-api-key", quick start and model selection.