Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/KevinZai/commandernpx agentmods add skills/kevinzai/commander/ccc-settingsWrote 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-settings)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-settings"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-settings.svg" alt="Measured on agentmods" 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.00038 | $0.01180 |
| Opus 5 | $0.00019 | $0.00590 |
| Sonnet 5 | $0.00008 | $0.00236 |
| Haiku 4.5 | $0.00004 | $0.00118 |
Grade D, and why
ccc-settings scanned grade D with 3 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 4d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
- If not set: show instructions to set the following in your shell config (`.bashrc`, `.zshrc`) or via your preferred secrets manager: Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/commander/config.json 2>/dev/null || echo '{}' Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- If confirmed: `rm -rf ~/.claude/commander/sessions/ ~/.claude/commander/knowledge/` How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-settings — Configuration hub
Placeholders like ~~project tracker refer to connected tools. See CONNECTORS.md.
Configuration hub for CC Commander. Reads from and writes to ~/.claude/commander/config.json. Full menu sourced from references/settings.json.
Quick Mode (default)
Load current config and show top 4 most-changed settings:
cat ~/.claude/commander/config.json 2>/dev/null || echo '{}'
Display current values and offer via AskUserQuestion (max 4 options — "Back to main menu" is a plain-text line below the picker, not a 5th chip):
- "Change my name" (currently: {name})
- "Change theme" (currently: {theme})
- "Set cost ceiling" (currently: ${costCeiling})
- "More settings..."
Below the picker: Or say "back" to return to /ccc.
Power Mode
Full settings menu from references/settings.json. Activate by passing --power or all as argument, or when user selects "More settings...".
Page the 8 settings below into two 4-option AskUserQuestion pickers (max 4 per AUQ) rather than one 8-item list — page 1: name, level, cost ceiling, theme; page 2: animations, Linear setup, launch mode, reset. A "More…" chip on page 1 cascades to page 2, same pattern as $ccc-more.
Available Settings
All options from references/settings.json. Entries marked (CLI-only) configure the ccc terminal binary and have no effect in Claude Code Desktop / Cowork Desktop — surface them anyway (users may run both), but note the scope.
a) Display name — How CC Commander addresses you
- Ask: "What name should I use?" → write to
config.json
b) Experience level — beginner / intermediate / expert
- Affects verbosity, auto-confirm thresholds, and suggested skill complexity
- Ask via AskUserQuestion with 3 options
c) Cost ceiling — Max budget per dispatch (default: $10)
- Ask: "Max budget per session?" → validate is a number → write to
config.json - Note: $10 hard ceiling in night-mode is separate
d) Theme (CLI-only) — Visual theme for ccc CLI
- Options: Claude Anthropic (default) / OLED Black / Matrix / Surprise Me
- Use Bash to apply if
ccc --themeis available; otherwise note takes effect on nextccclaunch
What ships with it
1 file 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.
- 4d ago First seen · 114 lines · 38 tokens per session scan D 8e794f6d2beb
ccc-settings is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 1,180 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it D with 3 findings (asks the agent to reveal its instructions, reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
prompt-library
Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-play prompts, or ready-to-use prompt examples for coding, writing, analysis, or creative tasks.
memstack-automation-n8n-workflow-builder
Use this skill when the user says 'n8n workflow', 'build a workflow', 'automation workflow', 'connect services', or needs visual workflow design with node mapping, data transformations, and error handling for n8n. Do NOT use for standalone webhook endpoints or cron jobs.
memstack-automation-cron-scheduler
Use this skill when the user says 'cron job', 'scheduled task', 'run every', 'cron expression', 'recurring job', or needs production-grade scheduled jobs with overlap prevention, monitoring, and structured logging. Do NOT use for n8n workflows or event-driven webhooks.
cco-clean
Clean up old tracking data and reset statistics.
search-first
A workflow rule for searching for an existing solution before writing new code. It checks the repository, internal mirrors, package registries, connected tools, and GitHub in that order.
multi-plan-handoff
Auto-detect plan files in conversation context and pass them to multi: execute subagents by reference, not by paraphrase.