JuliusBrussee/caveman

🪨 why use many token when few token do trick. Viral skill + proxy for coding agents that cuts 65% of tokens by talking like a caveman.

# why many token when few do trick **Caveman make your AI agent say less and read less. Code stay exact. Brain still big.** 33.2% fewer input tokens, whole sessions 54 Claude Code runs , 18 of 18 answers right 54% cheaper with Auto, same score 85 coding tasks vs Opus 5.5 at xhigh, interim 397 → 76 tokens for one test run Blocks vs | tail -20 1.4 to 2.4× cheaper with caveman-style output Adobe Research , eight models Cited by **[Adobe Research](https://arxiv.org/abs/2606.24083)** · A/B tested by **[JetBrains](https://blog.jetbrains.com/ai/2026/07/speak-to-ai-agents-like-cavemen-tosave-tokens/)** · Remade for Elasticsearch on **[Elasticsearch Labs](https://www.elastic.co/search-labs/blog/elastic-caveman-ai-token-reduction)** **#1** on [Hacker News](https://news.ycombinator.com/item?id=47647455) · **#1** on GitHub Trending · *"No way this actually works."* [ThePrimeagen](https://www.youtube.com/watch?v=L29q2LRiMRc) **[Install](#install) · [Six rocks](#six-rocks-one-install) · [Proof](#proof) · [Say less](#say-less-the-caveman-voice) · [Read less](#read-less-332-fewer-input-tokens) · [Auto](#auto-54-cheaper-same-score) · [Blocks](#blocks-code-mode-script-written-once) · [Commands](#commands) · [Caveman Cloud](#caveman-cloud)** --- Normal agent · 63 tokens Caveman agent · 20 tokens > The reason your React component is re-rendering is likely because you're creating a new object reference on each render cycle. When you pass an inline object as a prop, React's shallow comparison sees it as a different object every time, which triggers a re-render. I'd recommend using useMemo to memoize the object. > New object ref each render, so React re-renders. Wrap the prop in `useMemo`. **Same fix. 63 token become 20. Brain still big.** Pi