Five questions. No email. Your answers stay in your browser.
Updated 2026-05-05. The three books are written by yurukusa from 800+ verified hours of autonomous Claude Code operation.
QUESTION 1 OF 5
What is the most pressing thing on your mind about Claude Code right now?
QUESTION 2 OF 5
How long have you been running Claude Code in real work?
QUESTION 3 OF 5
Roughly what percentage of your Claude Code work is mechanical (formatting, classification, summarization, extraction)?
QUESTION 4 OF 5
How well does your team handle surprise output from Claude Code?
QUESTION 5 OF 5
What would success look like in 30 days?
RECOMMENDED
Token Book
Your answers point to the cost layer. The bill, the burn, the unknown. Token Book is built for exactly this entry point.
94 pages. Pay what you want, suggested $12. Chapter 1 is free at yurukusa.github.io/cc-safe-setup/token-book.html. The book covers measurement first (you cannot fix what you cannot see), then the six leak shapes, then the hooks that prevent each one.
If costs are bigger than your team can absorb in the next 30 days, the Migration Playbook covers the structural option (Path B hybrid delegation) that can move 17x more bulk work to a cheap side worker.
The Operations Suite page shows how all three books fit together if you want to plan ahead.
RECOMMENDED
Migration Playbook
Your answers point to the decision layer. Stay, hybrid, switch. Migration Playbook lays out the four paths side by side with the trade-offs you cannot get from a vendor blog.
105 pages. $19 on Gumroad. Edition 2 ships 2026-05-08; current buyers get the update for free. Covers Path A (stay and harden), Path B (hybrid with cheaper models), Path C (custom routing), and Path D (full migration), each with a cost-forecast worksheet and a 48-hour rollback plan.
Once you pick a path, the Token Book gives you the cost projection method for whichever direction you go.
If you might end up staying, the Incident Postmortems book documents the failure modes that survive on every path; read before committing.
RECOMMENDED
Incident Postmortems
Your answers point to the trust layer. Something broke or might break, and the team needs to see the failure shapes before they happen again. Postmortems is built for this entry point.
100 pages PDF. Live on Gumroad since 2026-05-05. Twelve real production incidents reverse-engineered from GitHub Issues, commits, and 800 plus hours of autonomous operation, each with a detection hook and a prevention path.
Once incidents are under control, the Token Book audits ongoing burn so the next surprise is not financial.
The Migration Playbook is the next step once you have evidence and need to decide whether to stay or move.
RECOMMENDED
Operations Suite (all three books)
Your answers say all three layers matter at once. The Operations Suite curation page maps the three books to three reader profiles and tells you the order to read them based on which problem to solve first.
Three books, 299 pages combined, $60 plus when bought separately. There is no shared discount SKU; the suite page is a navigation aid that tells you which book to start with for your specific situation, plus reading-order paths for the burn debugger, switch decider, and incident survivor profiles.