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-yolo-setupgit 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-yolo-setup)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-yolo-setup"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-yolo-setup.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.00054 | $0.01158 |
| Opus 5 | $0.00027 | $0.00579 |
| Sonnet 5 | $0.00011 | $0.00232 |
| Haiku 4.5 | $0.00005 | $0.00116 |
Grade B, and why
ccc-yolo-setup scanned grade B 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- label: "🌐 Global (~/.claude/settings.json)" How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-yolo-setup — Safe YOLO + Plan Mode
Reduce approval friction without going recklessly permissive. Safe-YOLO auto-approves a vetted allowlist of read-only / non-destructive operations, keeps Plan mode for anything that writes, deletes, or hits the network, and logs every auto-approval so the trail is auditable.
CC Commander · Reduce Approval Friction · Docs
What it does
- Allowlists safe, recurring commands — reads,
git status/log/diff/show,gh pr/issue/run view|list,ls/grep/find/cat/head/tail, read-only cloud describes/gets. No prompts for these. - Keeps Plan mode the default — risky changes (writes, deletes, deploys, force-push, network mutations) still surface a plan + approval.
- Audit logging — every auto-approved call is appended to
~/.claude/commander/auto-approve-log.jsonlso you can review what ran unattended.
What it does NOT do
- ❌ It never enables blanket
--dangerously-skip-permissions. - ❌ It never auto-approves writes, deletes,
rm,git push --force, deploys, or money/cloud-mutating commands. - ❌ It never touches secrets-printing commands.
Pick a profile (click-first)
Call AskUserQuestion:
question: "How aggressive should safe-YOLO be?"
header: "Safe-YOLO"
multiSelect: false
options:
- label: "🟢 Conservative"
description: "Auto-approve reads + git/gh read-only only. Everything else prompts. Safest."
- label: "🟡 Balanced (recommended)"
description: "Reads + git/gh reads + read-only cloud describes/gets + safe build/test. Plan mode for writes."
- label: "🔴 Aggressive-safe"
description: "Balanced + scoped writes inside the repo worktree. Still no deletes/deploys/force-push/network mutations."
Then ask where to apply:
question: "Apply to which scope?"
header: "Scope"
options:
- label: "🌐 Global (~/.claude/settings.json)"
description: "Every project + Desktop. Best for a single-user workstation."
- label: "📁 This project (.claude/settings.local.json)"
description: "Only this repo; gitignored so it doesn't ship to collaborators."
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 · 99 lines · 54 tokens per session scan B 1795ec2b8d5a
ccc-yolo-setup is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 1,158 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B 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
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.