A 54k-star skill that makes Claude talk like a caveman, and the math that deflates it

JuliusBrussee/caveman hit 54,000+ GitHub stars in under three weeks and topped Hacker News. The repo is exactly what it sounds like: a skill that strips agent verbosity, kills the "I'd be happy to help" preamble, and makes Claude answer in terse, near-grunt prose while keeping code blocks, error strings, and symbols intact. It's packaged for Codex, Gemini, Cursor, Windsurf, Cline, and Copilot too. The advertised number is ~65% average output reduction across 10 prompts.

I get the appeal. Watching a model spend 200 tokens telling you it's about to do the thing before it does the thing is genuinely annoying, and at scale it adds up. But the star count is doing a lot of work that the math doesn't support. andrew.ooo ran independent tests and landed at 30-50% output reduction, not 65%. More important: output tokens are a minority of your bill. The actual spend in a Claude Code session is dominated by thinking tokens and code generation, not conversational prose. By his estimate 80-90% of the bill lives in the parts caveman doesn't touch.

So this is a real tool aimed at the cheap part of the problem. Use it where output genuinely dominates. Chatty review loops, analysis passes, anything where the model is talking more than it's coding or thinking. Don't expect it to move your invoice if your workload is heavy generation.

The smarter read is that caveman is one of three independent tools all attacking agent token spend from different angles. claude-mem (82k stars) compresses cross-session memory. code-review-graph (18.4k stars) scopes context reads to a code graph so the agent reads only the relevant slice. Output stripping, memory compression, context scoping. Four major platforms reset their billing within about 18 days of each other this spring, and builders responded by stacking reducers across all three layers instead of betting on one. That's the actual story. Caveman is the loud one because it's funny. The category is the signal. If token cost is hurting you, pair output stripping with a context-side tool like a code graph and a memory layer. The single-lever fix doesn't exist.