Stats
Links
Categories
Vibe Better With Claude Code (Opus 4.6+) - YOLO
You're not an engineer anymore. You're a prompt jockey with commit access. At least do it properly.
Token Efficiency vs Stock Opus 4.6 Agent Teams
Native Rust CLI handles hooks, commands, and validation at zero model token cost. Codebase grew 64% since v1.20.0 while per-request overhead dropped 17%. 1,610 tests validate the stack.
Analysis reports: v1.21.30 | v1.20.0 | v1.10.7 | v1.10.2 | v1.0.99
| Category | Stock Agent Teams | YOLO | Saving |
|---|---|---|---|
| Base context overhead | 10,800 tokens | 1,500 tokens | 86% |
| State computation per command | 1,300 tokens | 200 tokens | 85% |
| Agent coordination (x4 agents) | 16,000 tokens | 1,200 tokens | 93% |
| Compaction recovery | 5,000 tokens | 700 tokens | 86% |
| Context duplication (shared files) | 16,500 tokens | 900 tokens | 95% |
| Agent model cost per phase | $2.78 | $1.40 | 50% |
| Total coordination overhead | 87,100 tokens | 12,100 tokens | 86% |
| Scenario | Without YOLO | With YOLO (Balanced) | Impact |
|---|---|---|---|
| API: single project (10 phases) | ~$28 | ~$14 | ~$14 saved |
| API: active dev (20 phases/mo) | ~$56/mo | ~$28/mo | |
| API: heavy dev (50 phases/mo) | ~$139/mo | ~$70/mo | |
| API: team (100 phases/mo) | ~$278/mo | ~$139/mo | |
| Pro / Max subscription | baseline capacity | ~3x phases per cycle | 200% more work done |
Budget profile ($0.70/phase) doubles API savings. Quality profile ($2.80/phase) matches stock cost but adds enforcement at zero premium.
What Is This
Platform: macOS and Linux only. Windows via WSL.
YOLO is a Claude Code plugin that bolts an actual development lifecycle onto your vibe coding sessions. You describe what you want, YOLO breaks it into phases, agents plan and verify the code, commits are atomic, and state persists across sessions. Inspired by Ralph and Get Shit Done, built from scratch.
What You Get
- One command lifecycle --
/yolo:vibeauto-detects state and runs the right workflow (scope, plan, execute, archive) - 8 specialized agents with platform-enforced tool permissions via subagent_type routing -- Debugger is read-only (
planmode), Reviewer and QA are write-restricted - 19 hook handlers across 11 event types -- continuous verification, security filtering, session lifecycle
- Atomic commits per task with conventional format, auto-push optional
- Session persistence -- close your terminal, come back tomorrow,
/yolo:resumepicks up where you left off - 4 effort profiles (Thorough/Balanced/Fast/Turbo) and 4 autonomy levels (Cautious to Pure Vibe)
- Database safety guard -- blocks 40+ destructive patterns across all major frameworks before they hit the shell
- Skills.sh integration -- auto-detects your stack, suggests and installs community skills
Quick Start
Two commands, one lifecycle.
/yolo:init # scaffold environment, detect stack, suggest skills
/yolo:vibe # auto-detects state: scope -> plan -> execute -> archive
/yolo:vibe is the only command you need to remember. Run it repeatedly -- it picks up where the last invocation left off. State persists in .yolo-planning/ across sessions.
Existing codebase? /yolo:init auto-chains /yolo:map (4 parallel Scout teammates analyze your code) before /yolo:vibe.