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 skills add KevinZai/commander --skill ccc-codexgit clone --depth 1 https://github.com/KevinZai/commanderWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/kevinzai/commander/ccc-codex)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-codex"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-codex/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-codex"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-codex.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00059 | $0.03507 |
| Opus 5.5 | $0.00024 | $0.01403 |
| Sonnet 5.5 | $0.00012 | $0.00701 |
| Haiku 4.5 | $0.00006 | $0.00351 |
Grade A, and why
ccc-codex 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 3d ago.
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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-codex — manage the Codex CLI
CC Commander · $ccc-codex · check, configure and extend the local Codex CLI without leaving the session
When to use / when not to
- Use to diagnose Codex, pick its default model, install Commander's Codex plugin, add MCP servers or custom agents, run Codex reviews or cloud tasks, or change Codex config and feature flags.
- Do not use to delegate a whole implementation task to Codex; use
$ccc-orchestrate. - Do not use for Claude Code settings; use
$ccc-settings.
Reference tables live beside this file: references/models.md (model lineup and effort levels), references/commands.md (every subcommand and flag used here), references/config.md (config keys, feature flags, profiles, marketplace format).
What happens
Step 0 — preflight (every subcommand)
command -v codex && codex --version
CODEX_HOME_DIR="${CODEX_HOME:-$HOME/.codex}"
CODEX_CONFIG="$CODEX_HOME_DIR/config.toml"
echo "$CODEX_CONFIG"; [ -f "$CODEX_CONFIG" ] && echo "config present" || echo "no config yet"
If codex is missing, stop and say: "Codex CLI not found. Install it with npm install -g @openai/codex, then rerun $ccc-codex doctor." Honor CODEX_HOME everywhere below; never assume ~/.codex when it is set.
Step 1 — route
If $ARGUMENTS names a subcommand, go to that section. On a bare invocation, ask with AskUserQuestion (header "Codex"); on Codex itself, ask the same options as a numbered plain-text question:
- 🟢 Health check —
codex doctor, then the fix for whatever fails - Models and config — default model, effort, feature flags, profiles, update, import
- Extensions — plugins (including Commander's mirror), MCP servers, custom agents
- Run work — review, cloud tasks, remote control
Then ask a second picker with the subcommands in the chosen group.
Config backup (before any change to config.toml)
Every command that writes config (features enable|disable, mcp add|remove, plugin add|remove, plugin marketplace add|remove, a model or profile edit) runs only after the user confirms, and only after this backup:
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 241 lines · 59 tokens per session scan A b26235367901
ccc-codex is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 3,507 once invoked, about $0.0002 per session on Opus 5.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-10-14.
Other skills, from other repositories
uninstall
Remove Multi startup files while preserving provider credentials.
login
Start the official Cursor SDK login flow.
skill-dev
Use this skill when creating or refining Claude Code skill definitions. Skills are model-invoked capabilities that Claude activates autonomously based on context. Helps design focused skills with discovery-optimized descriptions, proper directory structures, and supporting resources. Automatically invoked when user…
command-dev
Use this skill when creating or refining custom Claude Code slash commands. Slash commands are user-invoked reusable prompts that can accept arguments, reference files, and execute bash operations. Helps design command syntax, argument handling, file references, bash execution, and frontmatter configuration.…
coordinator
Runs the research-team plugin's multi-agent research pipeline end-to-end from the main thread: decomposes a topic into 2-5 subtopics, spawns parallel research-team:research-specialist subagents for each, verifies their output on disk, then spawns a research-team:research-report-writer subagent to synthesize the final…
mcp-tool-dev
Create MCP tools — individual tool functions exposed via Model Context Protocol. Use this skill whenever users mention MCP tools, tool handlers, tool functions, tool definitions, or want to add capabilities to an MCP server. Also use when the conversation involves designing tool schemas, writing tool descriptions, or…