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-tuneupgit 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-tuneup)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-tuneup"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-tuneup.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.00049 | $0.06232 |
| Opus 5 | $0.00024 | $0.03116 |
| Sonnet 5 | $0.00010 | $0.01246 |
| Haiku 4.5 | $0.00005 | $0.00623 |
Grade A, and why
ccc-tuneup scanned grade A with 1 finding 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
| `SETTINGS_MISSING_KEYS` | settings.json keys absent from global `~/.claude/settings.json` | Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 421 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-tuneup — Local Setup Optimizer
The companion to $ccc-doctor. Doctor diagnoses (read-only). Tune-up remediates — but safely: read-only scan first, backup before any edit, archive (never rm) for junk, and an explicit click-to-confirm before anything mutates.
CC Commander · Tune-Up · Docs
Arguments
--check— read-only audit + scorecard. NO prompt, NO mutation. (Default if the user seems unsure.)--fix— audit, then offer safe fixes via AskUserQuestion chips (destructive-leaning items OFF by default).--aggressive— same as--fixbut pre-selects session archival + superseded-agent retirement chips.- bare
$ccc-tuneup— runs the audit, shows the scorecard, then opens the chip picker.
Safety rules (NON-NEGOTIABLE)
- ❌ NEVER
rmortrashanything — junk moves to~/.claude/commander/tuneup-archive/<UTC-stamp>/. - ✅ Before editing
settings.jsonor anyCLAUDE.md:cp <file> <file>.backup-$(date +%Y%m%d-%H%M%S). - ❌ NEVER edit
~/.claude/CLAUDE.mdor any file under~/.claude/**— the user's global config may contain plugin-count strings that are NOT ours to rewrite. - ❌ NEVER edit a CLAUDE.md unless the
git rev-parse --show-toplevelof the target file resolves to a cc-commander checkout (verified by:basename $(git -C <dir> rev-parse --show-toplevel)= "cc-commander" ANDtest -f <root>/scripts/audit-counts.js). For end-user installs (no git root, or clone under~/.claude/plugins), the CLAUDE.md-count row is DETECT-ONLY — show the drift, do NOT offer to fix it. - ❌ NEVER run
git pull,openclaw/Desktop restarts, or marketplace re-adds — emit them as copy-paste terminal commands. - ❌ NEVER mutate the plugin clone's own source files unless running from a verified cc-commander git root.
- ✅ Every count is computed LIVE from the filesystem and manifests — NEVER hardcode "61 skills" / "23 events" / a version.
- ✅ Take ALL backups first; apply; on ANY failure restore ALL backups taken this run (ordered rollback).
- ✅ Re-read each file immediately before each Edit and stat-compare to scan; if changed since scan, skip the fix and report "file changed since scan — skipped".
- ✅ Keep only the last 3
*.backup-<ts>per file; offer to archive older ones into tuneup-archive.
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.
- 3d ago First seen · 421 lines · 49 tokens per session scan A 42f4d7a3a08c
ccc-tuneup is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 6,232 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
multi-plan-handoff
Auto-detect plan files in conversation context and pass them to multi: execute subagents by reference, not by paraphrase.
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.…
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…
debt-ops-init
Write or refresh a "Tech debt operations" section in the project's AGENTS.md so the team shares one source of truth for debt-ops disciplines. Run ONLY when the user explicitly asks to set up, install, or initialize debt-ops disciplines — never auto-invoke. Idempotent; only the managed section changes, other sections…
debt-ops-metrics
Print a debt-ops health summary from the metrics log, covering registration rate, feedback action rate, ADR creation, and AI-authored share. Use when the user asks for "debt-ops metrics", "debt health", "registry stats", or a tech-debt health summary. Read-only, never writes the log.