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-adoptgit 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-adopt)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-adopt"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-adopt/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-adopt"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-adopt.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 7 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium Rogue Agent · line 10 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 32 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 226 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 73 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Output Handling · line 197 Output size or generation rate is not bounded. Unbounded output enables denial-of-service through resource exhaustion, log flooding, or context-window stuffing.Fix: Set explicit limits on output length, generation count, and rate. Use max_tokens and truncation to prevent unbounded output.
- medium Excessive Agency · line 222 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00058 | $0.03040 |
| Opus 5.5 | $0.00023 | $0.01216 |
| Sonnet 5.5 | $0.00012 | $0.00608 |
| Haiku 4.5 | $0.00006 | $0.00304 |
Grade A, and why
ccc-adopt 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 8d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-adopt — Commander conventions, your repo
CC Commander · $ccc-adopt · one delimited CLAUDE.md block plus skill pointers for your stack, never a clobber.
Runs inside any project other than Commander's own. It adds Commander's orchestrator/executor section and a stack-tailored pointer list to that project's CLAUDE.md, between markers so a re-run replaces the block instead of duplicating it.
On Codex, AskUserQuestion becomes a plain-text question with the same options; every other step is identical.
When to use / when not to
- Use once per existing project, and again after the stack changes (the re-run replaces the block in place).
- Use
$ccc-onboardto onboard a contributor to a repository (including Commander's own),$ccc-tuneupto tune the local Commander install under~/.claude, and$ccc-claudemdto rewrite a whole CLAUDE.md.
Arguments
--check— read-only: detect stack, CLAUDE.md and marker state, print the plan from step 4, write nothing.- No argument — detect, preview the diff, write on approval.
What happens
Shell state does not persist between Bash calls: start each later command with ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd) and use the literal backup path printed in step 6.
1. Detect
GIT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || echo "")
ROOT="${GIT_ROOT:-$PWD}"
echo "GIT_ROOT=${GIT_ROOT:-n/a}"
echo "HAS_CLAUDE_MD=$([ -f "$ROOT/CLAUDE.md" ] && echo yes || echo no)"
echo "HAS_MARKER=$(grep -q 'CCC:orchestrator-executor:start' "$ROOT/CLAUDE.md" 2>/dev/null && echo yes || echo no)"
# Stack signals
test -f "$ROOT/package.json" && echo "STACK=node" && grep -o '"\(react\|next\|vue\|nuxt\|express\|fastify\|hono\)"' "$ROOT/package.json" 2>/dev/null
test -f "$ROOT/pyproject.toml" -o -f "$ROOT/requirements.txt" && echo "STACK=python"
test -f "$ROOT/Cargo.toml" && echo "STACK=rust"
test -f "$ROOT/go.mod" && echo "STACK=go"
test -f "$ROOT/Gemfile" && echo "STACK=ruby"
test -f "$ROOT/composer.json" && echo "STACK=php"
test -f "$ROOT/pom.xml" -o -f "$ROOT/build.gradle" && echo "STACK=jvm"
test -d "$ROOT/.github/workflows" && echo "SIGNAL=ci"
ls "$ROOT"/app.json "$ROOT"/Podfile "$ROOT"/*.xcodeproj 2>/dev/null | head -1 | sed 's/^/SIGNAL=mobile /'
# Package manager
test -f "$ROOT/bun.lockb" -o -f "$ROOT/bun.lock" && echo "PM=bun"
test -f "$ROOT/pnpm-lock.yaml" && echo "PM=pnpm"
test -f "$ROOT/yarn.lock" && echo "PM=yarn"
test -f "$ROOT/package-lock.json" && echo "PM=npm"
# Commander's own repo?
{ [ "$(basename "$ROOT")" = "cc-commander" ] || [ -f "$ROOT/scripts/audit-counts.js" ] || [ -f "$ROOT/commander/cowork-plugin/.claude-plugin/plugin.json" ]; } && echo "SELF=yes"
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.
- 8d ago Changed · -3 lines · +9 tokens per session 289e2adb6823
- 1mo ago First seen · 236 lines · 49 tokens per session scan A 48b8ee2e557f
ccc-adopt is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 3,040 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-08-31.
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…