ccc-yolo-setup

ccc-yolo-setup is a skill for Claude Code from KevinZai/commander. It costs 60 tokens per session (1,779 once invoked), scanned B, original, MIT.

A permission setup that automatically approves a limited list of read-only or non-destructive operations while keeping risky changes behind Plan mode and approval. It records each automatic approval for later review.

In plain words
What is it for?
Use it when inspecting repositories, viewing GitHub information, checking Git history, or reading safe cloud details during development.
Why use it?
It reduces repeated approval prompts without giving the coding agent unrestricted permission to write, delete, deploy, or change cloud resources.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; names the AskUserQuestion tool; mentions Claude Code.

Good fit Use it when inspecting repositories, viewing GitHub information, checking Git history, or reading safe cloud details during development.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kevinzai/commander/ccc-yolo-setup
Install

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.

Any agent
npx skills add KevinZai/commander --skill ccc-yolo-setup
Clone the repo
git clone --depth 1 https://github.com/KevinZai/commander

Made for: Claude Code.

Wrote 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.

agentmods badge for ccc-yolo-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/kevinzai/commander/ccc-yolo-setup/github.svg)](https://agentmods.dev/skills/kevinzai/commander/ccc-yolo-setup)
Your own site
<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-yolo-setup"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-yolo-setup/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.

agentmods 80×15 button for ccc-yolo-setup

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,779 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00060 $0.01779
Opus 5.5 $0.00024 $0.00712
Sonnet 5.5 $0.00012 $0.00356
Haiku 4.5 $0.00006 $0.00178

Measured yesterday against content hash 39d8c8454653, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 yesterday.

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.

for f in ~/.claude/settings.json .claude/settings.local.json .claude/settings.json; do
commander/cowork-plugin-codex/skills/ccc-yolo-setup/SKILL.md · 138 lines

How it starts

The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.

$ccc-yolo-setup — safe YOLO permissions

CC Commander · $ccc-yolo-setup · fewer prompts on safe operations, the auto-mode classifier on everything else, and a backup to roll back to.

Interactive Claude Code sessions start in auto permission mode when no mode is configured: a classifier approves routine actions and denies risky ones without a prompt. Safe-YOLO builds on that default. It adds a vetted allowlist of read-only and non-destructive commands, adds deny rules for secret files, and leaves risky work (writes outside scope, deletes, deploys, force-push, network mutations) to the classifier or a prompt. Plan mode stays available on request for risky changes.

When to use / when not to

  • Use when routine reads, git/gh reads or cloud describes keep prompting.
  • Use /fewer-permission-prompts (built in) to mine the user's own transcripts for further safe entries.
  • Do not use to approve writes, deletes, deploys or cloud mutations; those stay gated.
  • revert jumps to Reverse it.

What happens

1. Read the current state

for f in ~/.claude/settings.json .claude/settings.local.json .claude/settings.json; do
  [ -f "$f" ] && node -e 'const s=JSON.parse(require("fs").readFileSync(process.argv[1],"utf8"));const p=s.permissions||{};console.log(process.argv[1]+": defaultMode="+(p.defaultMode||"unset (auto)")+" allow="+(p.allow||[]).length+" deny="+(p.deny||[]).length)' "$f"
done

Report each line. A parse error means the file is already invalid JSON: stop and show the error; do not write to it.

2. Pick a profile

Ask with AskUserQuestion (Codex: plain-text question):

question: "How much should safe-YOLO auto-approve?"
header: "Profile"
options:
  - label: "🟢 Balanced"
    description: "Reads, git/gh reads, read-only cloud describes, and this repo's test/lint/build scripts."
  - label: "Conservative"
    description: "Reads and git/gh read-only only. Everything else goes to auto mode or a prompt."
  - label: "Aggressive-safe"
    description: "Balanced plus file edits scoped to this repo. Still no deletes, deploys, force-push or network mutations."

Read the full file on GitHub · 138 lines

Files

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.

Changes

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.

  1. yesterday Changed · -2 lines 39d8c8454653
  2. 3d ago Changed b1664820ca1e
  3. 14d ago Changed · +41 lines · +6 tokens per session b6ffc0a1e452
  4. 1mo ago First seen · 99 lines · 54 tokens per session scan B 1795ec2b8d5a

Subscribe to this mod's changes

ccc-yolo-setup is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 1,779 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories

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.

cwinvestments/memstack · 68 tokens

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.

cwinvestments/memstack · 67 tokens

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.

LeeYudok/agents-scaffold · 117 tokens

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…

bcanfield/agentic-tech-debt · 76 tokens

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.

bcanfield/agentic-tech-debt · 74 tokens

knowledgebase

Generate professional multi-page HTML knowledge bases and study guides for software engineering, data science, and AI/ML work — field guides, solution handbooks, service catalogs, team runbooks, onboarding documentation, and technical study resources. Produces self-contained, offline-capable HTML sites with sidebar…

andisab/swe-marketplace · 213 tokens