Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/kevinzai/commander/ccc-night-mode)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-night-mode"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-night-mode.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.00047 | $0.01458 |
| Opus 5 | $0.00023 | $0.00729 |
| Sonnet 5 | $0.00009 | $0.00292 |
| Haiku 4.5 | $0.00005 | $0.00146 |
Grade C, and why
ccc-night-mode scanned grade C 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 6d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Never run `rm -rf` without explicit user confirmation How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-night-mode — Autonomous overnight build
Placeholders like ~~project tracker refer to connected tools. See CONNECTORS.md.
Autonomous build system for unattended work. Two modes: Night Mode (spec now, build overnight, 8-hour scheduled run) and YOLO Mode (spec now, build immediately, no confirmations). Full menu in references/autonomous-mode.json.
Quick Mode (default)
Ask the user which mode via AskUserQuestion:
- Night Mode — scheduled overnight run, starts building when you close your laptop
- YOLO Mode — starts immediately, no confirmations, maximum autonomy
- Monitor & Maintain — watch CI, fix builds, guard tests (recurring loop)
- Cancel / Back to main menu
Then proceed to the 10-question Spec Interview.
Power Mode
Full autonomous mode menu from references/autonomous-mode.json. Activate by passing --power or detailed. Includes:
- Monitor & Maintain (PR Babysitter, Build Shepherd, Test Guardian, PR Pruner, Dependency Watcher, Cost Monitor)
- Background Coding (implement from spec, post-merge sweep, doc updater, knowledge compounder)
- Batch Operations (CJS→ESM, class→hooks, multi-file rename, dependency upgrade, lint rule enforcement)
- Custom Loop (describe what + how often)
Spec Interview (10 Questions — ALL required before autonomous execution)
Ask every question. Do not skip or assume.
- What are you building? — Full project description
- Who is it for? — Target users/audience
- Most critical feature? — The one thing that MUST work
- Tech stack? — Languages, frameworks, databases, infrastructure
- What does DONE look like? — Specific acceptance criteria
- What does BROKEN look like? — Failure modes to prevent
- Edge cases? — Known tricky scenarios to handle
- Testing requirements? — Unit, integration, E2E expectations
- Deployment target? — Where it runs (Vercel, AWS, Docker, local)
- Anything else? — Additional context, constraints, API keys needed
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.
- 6d ago First seen · 128 lines · 47 tokens per session scan C 5131c4ad31fb
ccc-night-mode is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 1,458 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
session-relay
Continue real repository work between Claude Code, Codex CLI, and Grok Build with a privacy-bounded, drift-aware handoff packet. Use for cross-vendor takeover, context-limit checkpoints, multi-hop Claude→Codex→Grok relays, or receiving an existing Director packet. Use native resume commands for same-CLI history; never…
handoff
Create a self-contained temporary handoff document when the user asks to transfer the session to a new chat or runs /handoff.
create-handoff
Create handoff document for passing work to another session. ALWAYS use when the user says 'create a handoff', 'hand this off', 'save progress for later', 'I need to stop here', or when context usage is high (>60%) during implementation and work needs to continue in a fresh session.
setup-warp
Interactively configure Warp terminal as a Catalyst launcher. Checks Warp install, detects projects, interviews the user for display details (name/emoji/color/variants) and generates /.warp/tabconfigs/.toml files with session-naming and remote-control wiring. Idempotent — re-run to add or update projects.
human-ai-schedule
Co-author doctrine for shared, half-hour-block daily schedules. Make sure to consult this skill whenever working in a dated daily log, journal, retro, or coordination file shared with a coworker — even if the user only says "log this at 11:00" or "what did we say last Tuesday." Default behavior of dumping procedural…
morning-briefing
Generate a daily briefing markdown at thoughts/briefings/YYYY-MM-DD.md with six sections — Review yesterday, Surface decisions, Plan today, relay-dispatch candidates, Friction since last briefing, and Learnings since last briefing — synthesized from Linear, GitHub, Granola, Google Drive, Google Calendar, and the…