The Viral Dev Hack · April 2026

Someone Taught Claude

To Talk Like a Caveman. Token Use Dropped 75%.

A Reddit post with 10,000 upvotes. A GitHub repo with 51,690 stars. A research paper that says less word equals more correct. The caveman prompt is the AI cost hack that should not work but absolutely does.

SENAARAVICHANDRAN A · IT STUDENT · PUDUCHERRY · MAY 2026

S omewhere between genuine engineering insight and performance art, a Reddit post appeared on r/ClaudeAI on April 3, 2026, with a title that did not sound like it was written by someone who wanted to be taken seriously: “Taught Claude to talk like a caveman to use 75% less tokens.” Within hours it had 10,000 upvotes and 400 comments. Half the comments were laughing. The other half were already installing the thing. By the next morning it had a GitHub repo. By the end of the week it had over 20,000 stars. By May 1, 2026, the repo had 51,690 stars and a research paper backing up the claim that making your AI speak in grunts does not just save money. It might actually make it smarter.

The mechanic is so simple it sounds like a joke. Instead of letting Claude open with “I’d be happy to help you with that,” narrate every tool it uses, explain its reasoning in three paragraphs, and close with “let me know if you need anything else,” you tell it to respond like a prehistoric human. Drop the articles. Drop the pleasantries. Drop the preamble. Execute first, result second, nothing else. A web search task that normally costs around 180 output tokens drops to about 45. The verbal equivalent of replacing “I executed the web search tool and retrieved the results you requested” with “Tool work.” The same information. A fraction of the tokens.

The original Reddit post has been attributed to a user called flatty, though the idea was quickly amplified and appropriated across social media, with several accounts claiming authorship before correction. The important chain of events is what happened next. Developer Drona Gangarapu packaged the concept into a benchmarked CLAUDE.md file on GitHub (3,300 stars). Developer Julius Brussee formalised it into a full SKILL.md spec with three compression modes, eval harnesses, companion tools, and compatibility with over 30 AI agents. The community took it from a joke post to a production tool in under 48 hours.

To understand why the caveman hack matters financially, you need to understand one counterintuitive fact about how large language model pricing works. Input tokens and output tokens are not priced the same. Not even close. As of early 2026, Claude Sonnet charges roughly $3 per million input tokens and $15 per million output tokens. Output tokens cost approximately four to five times more than input tokens for the same model. The reason is computational: generating each output token requires a forward pass through the full model, which is genuinely expensive to run, while reading input tokens is comparatively cheap.

What this means in practice is that every “I’d be happy to help you with that!” is not just an aesthetic annoyance. It is a line item. Every preamble paragraph explaining what Claude is about to do before it does it costs real money. Every closing offer to assist further costs money. Every mid-task narration of which tool is being called costs money. For a developer running an agentic Claude Code workflow with 30 to 40 task turns per session, those padding tokens are not negligible. They are a meaningful fraction of the bill, and they contain zero technical information the developer needed.

The caveman prompt targets precisely this output verbosity, and nothing else. It does not touch input tokens. It does not touch the conversation history or system prompt that Claude re-reads on every turn. It does not touch code blocks. It does not touch the internal reasoning and thinking tokens that the model runs before producing output. It makes only the final prose output smaller, by removing everything that serves politeness rather than purpose.

Here is where honest reporting requires a caveat that most of the viral coverage skipped, and that the Julius Brussee repo itself addresses directly in its evaluation harness. The 75% figure is real, but it applies specifically to prose output tokens. In a real Claude Code session, prose output is only one component of the total token usage. The conversation history, system prompt, any attached files, and tool call results constitute input context that grows with every turn and typically dwarfs the output. When you count everything, the session-wide savings are smaller.

Developer Kuba Guzik ran 72 independent test sessions to find out what the real number is. His conclusion: session-wide savings land between 14% and 21% when input tokens are properly counted. That is still meaningful at scale, but it is not the headline number. Perhaps more interestingly, Guzik also found that a six-line micro-prompt he distilled from the full caveman skill outperformed the full 552-token skill on both Claude Sonnet and Opus, with zero quality loss across all 72 runs. The minimum viable version of the idea outperformed the elaborate one.

The GitHub repository that turned the Reddit observation into a production tool is called simply “caveman” and lives at JuliusBrussee/caveman. Its tagline, written entirely in caveman-speak, reads: “why use many token when few token do trick.” The README is written in the same register throughout. When explaining that the tool does not impair reasoning quality, it states: “Caveman no make brain smaller. Caveman make mouth smaller.” This is either the cleverest or the most effective technical documentation of 2026, depending on how many GitHub stars you think good writing is worth.

The repo has three compression levels. Caveman Lite drops articles, filler words, and pleasantries while keeping complete sentences. Caveman Full switches to fragment grammar: no articles, no full sentence structure, everything compressed to its minimum meaningful form. Caveman Ultra is described in the README as “ancient scholar on a budget,” aimed at developers who want maximum compression and are comfortable reading telegraphic output at speed. There is also a fourth mode called Wenyan, named after the classical Chinese literary register, which outputs responses in classical Chinese characters. The README notes that classical Chinese is the most token-efficient written language humans ever invented: an entire sentence of English meaning can be compressed into two or three characters. This is not a practical tool for most developers, but it is a remarkable demonstration of what “maximum compression” can actually mean when you expand the definition of language.

The companion tools are where the repo becomes genuinely useful beyond the novelty. Caveman Commit writes git commit messages in 50 characters or fewer, in Conventional Commits format, with the emphasis on why rather than what. Caveman Review generates one-line code review comments in the format: line number, severity emoji, category, finding, recommendation. A normal code review comment might read: “On line 42, I noticed that you’re not checking whether the user object is null before accessing the name property. This could potentially lead to a TypeError in production. I’d recommend adding a null guard here.” The caveman equivalent: “L42: bug: user null. Add guard.” Same diagnostic value. Thirty-three fewer words.

The most surprising dimension of the caveman story is not the token savings. It is a research paper that appeared on arXiv in March 2026, catalogued as 2604.00025, titled “Brevity Constraints Reverse Performance Hierarchies in Language Models.” The researchers evaluated 31 open-weight models ranging from 0.5 billion to 405 billion parameters across 1,485 problems spanning five benchmark datasets covering mathematical reasoning and scientific knowledge. They applied brevity constraints to some runs and measured what happened to accuracy.

The finding that broke standard assumptions: brevity constraints improved accuracy by 26 percentage points on problems where verbosity was causing errors. On 7.7% of benchmark problems, larger models underperformed smaller ones when allowed to be verbose, by up to 28.4 percentage points. A 2-billion-parameter model beating a 400-billion-parameter model, not on a trick question, but on standard mathematical reasoning benchmarks. The mechanism the researchers identified is called spontaneous scale-dependent verbosity: larger models, trained on more data, have more tendency to overelaborate, hedge, explore tangents, and reason themselves into wrong answers through excessive inference steps. By forcing brevity, you cut the tangents and the hedging, and the model arrives at the correct answer faster and more often.

There is an important caveat the research itself flags, and that honest coverage of this story requires repeating: the paper evaluated open-weight models, not closed frontier APIs like Claude. Whether the same accuracy improvement applies to Claude Sonnet or Opus is an open empirical question that has not been definitively tested with the same rigour. The directional finding, that verbosity is not always a proxy for intelligence and that constraint can improve accuracy, is supported. The specific magnitude of the effect on commercial models remains uncertain.

The caveman documentation itself is clear about this, and it deserves more prominence than it gets in the viral coverage. Caveman mode is built for experienced developers who already understand the domain they are working in. The output tokens it removes are not filler for that audience. But for someone still learning, those tokens are not padding. They are the lesson. The explanation of why a React component is re-rendering because of inline object references on every render cycle is exactly what a junior developer needs. Caveman removes precisely that explanation and leaves only the useMemo fix. For a junior developer, that is not a savings. It is the difference between understanding and copying.

There are also task categories where verbosity is doing genuine cognitive work. Debugging sessions where the root cause is unclear, architecture discussions where multiple valid approaches need comparison, and learning conversations where the user is building a mental model rather than executing a known task: all of these benefit from the fuller response that caveman removes. The developers who benefit most from this tool are the ones who have already built the mental model and are now in execution mode, doing repetitive implementation work at speed. That is a large fraction of daily professional development work. But it is not all of it, and treating the tool as a universal default is how you strip away the responses you needed.

I study information technology in Puducherry, which means my relationship with AI token costs is structurally different from a developer at a San Francisco startup burning $30 a day on Claude API calls. I use Claude through claude.ai. I am not billing token usage to a corporate card. But the idea at the centre of the caveman hack is something I have been thinking about in a different register, because it is fundamentally a problem about information architecture.

What the caveman prompt actually does is force Claude to separate signal from noise in its own output. The words that carry technical information stay. The words that perform helpfulness disappear. In IT systems design, we call this data compression, and the principle is identical: find the minimum representation of the information that preserves its meaning. Claude without caveman mode generates output optimised for a certain kind of reader, one who needs reassurance that the AI is engaged, one who benefits from narration of each step, one who appreciates a closing offer. The caveman mode re-optimises the output for a different reader: one who already knows the domain, wants only the answer, and is measuring the tool by how quickly it returns value, not how warmly it communicates.

What I find genuinely surprising about the arXiv paper, sitting here in a classroom where we talk about prompt engineering as an emerging professional skill, is that the constraint that improves cost efficiency also improves accuracy. Those should not both be true at the same time. Making something cheaper should, intuitively, cost you something in quality. The finding that it does not, that the forced brevity cuts overelaboration before it becomes an error, that less word can equal more correct, is the kind of counterintuitive result that rearranges assumptions. It is the kind of result that is worth knowing even if you never install a single Claude Code plugin. It says something true about how intelligence, both artificial and otherwise, can get worse the more room it is given to elaborate.

Sources: JuliusBrussee/caveman GitHub repository (accessed May 2026) · Decrypt, “Devs Are Making Claude Talk Like a Caveman to Cut Costs — And It Works” (April 7, 2026) · Nathan Onn, “Claude Code Caveman Mode: Save more than 75% on Usage” (nathanonn.com, April 2026) · MayhemCode, “Caveman Claude Code: How to Save Tokens” (April 2026) · BlueMint Services, “Claude Caveman Prompt” (April 2026) · Pasquale Pillitteri, “Claude Code Caveman Mode: the Skill That Cuts Tokens Without Breaking Code” (April 14, 2026) · arXiv preprint 2604.00025, “Brevity Constraints Reverse Performance Hierarchies in Language Models” (March 2026) · Kuba Guzik independent benchmark, 72 test sessions (cited via BlueMint and Decrypt) · Drona Gangarapu CLAUDE.md benchmarks (3.3K stars, GitHub, April 2026) · DEV Community, “Caveman Claude: The Token-Cutting Skill That’s Changing AI Workflows” (April 5, 2026) · Paweł Huryn, X post (April 2026, includes attribution note re: original Reddit source flatty) · Claude API output token pricing confirmed via Anthropic pricing page (early 2026).