Skip to content
gentic.news — AI News Intelligence Platform
Connecting to the Living Graph…

Listen to today's AI briefing

Daily podcast — 5 min, AI-narrated summary of top stories

A bar chart comparing token usage between standard Claude Code and the Caveman skill, showing an 8.5% reduction in…

The Caveman Skill for Claude Code Saves 8.5% Tokens

Caveman skill for Claude Code saves 8.5% tokens, not 65%. Safe to use with no quality loss. Install via SkillsBench.

·1d ago·3 min read··15 views·AI-Generated·Report error
Share:
Source: blog.jetbrains.comvia jetbrains_ai_blog, hn_claude_code, gn_mcp_protocol, devto_mcpWidely Reported
How many tokens does the Caveman skill actually save in Claude Code?

The Caveman skill for Claude Code saves about 8.5% of output tokens on real agentic tasks, not the advertised 65%. It's safe to use with no quality degradation, but the savings come from compressing narration between tool calls, which is minimal in agentic workflows.

TL;DR

JetBrains' benchmark shows Caveman skill saves ~8.5% tokens on agentic tasks, not 65%, but doesn't degrade output quality.

Key Takeaways

What Changed — The Real Numbers Behind Caveman

JetBrains ran a proper A/B benchmark on the popular "Caveman" skill for Claude Code, and the results are sobering. The skill, which promises to "make agent talk like caveman" and save 65% of output tokens, actually delivers about 8.5% savings on real agentic tasks.

The key insight: agentic output is fundamentally different from chat. Claude Code's responses are dominated by code, diffs, tool invocations, and exact error strings — all of which Caveman correctly leaves verbatim. Only the narration between tool calls gets compressed, and there isn't much of it.

What It Means For You — Safe, Honest, Oversold

The good news: Across 82 paired tasks, JetBrains found zero detectable quality degradation. The skill changes how Claude Code talks without damaging what it produces. Code artifacts stay untouched and normal.

The bad news: The 65% claim is misleading for Claude Code users. That number comes from chat-style prose where narration dominates. In agentic workflows, where most tokens are code and commands, the ceiling is ~10%.

The cost reality: The 8.5% token savings should translate to ~10% cost reduction. However, JetBrains observed a single outlier task where the Caveman arm ballooned past the 200k long-context pricing tier, making it 11.6% more expensive overall. This is a task property, not a skill bug, but it's worth noting.

Try It Now — Should You Install Caveman?

Yes, but with adjusted expectations. Install it via SkillsBench:

Denis Shiryaev

# Install Caveman skill
claude code skill install caveman

When to use it:

  • When you want terser narration between tool calls (no quality loss)
  • When every token counts on long-running tasks
  • When you're hitting context limits frequently

When to skip it:

  • If you're relying on Claude Code's reasoning narration for debugging
  • For short, single-step tasks where 8.5% savings is negligible
  • If you're already using a "be brief" style prompt in CLAUDE.md (you're getting similar savings for free)

Pro tip: Add this to your CLAUDE.md for a lighter, zero-dependency alternative:

# Style preferences
Be concise in narration. Focus on code and commands.

The Bottom Line

Caveman is safe, honest about style, and oversold on savings. Install it if you want slightly terser agents. Don't expect the 65% savings advertised. For most Claude Code users, the real value is in the quality guarantee — you can compress narration without breaking output.


Source: blog.jetbrains.com

Source: gentic.news · · author= · citation.json

AI-assisted reporting. Generated by gentic.news from multiple verified sources, fact-checked against the Living Graph of 4,300+ entities. Edited by Ala SMITH.

Following this story?

Get a weekly digest with AI predictions, trends, and analysis — free.

AI Analysis

Claude Code users should adjust their expectations for token-saving skills. The Caveman skill's 8.5% savings on agentic tasks means you shouldn't rely on it alone for significant cost reduction. Instead, focus on techniques with proven larger impact: optimizing CLAUDE.md to reduce unnecessary context, using specific tool calls over verbose alternatives, and monitoring long-context pricing tiers. For developers considering Caveman, the safe deployment path is clear: install it, verify it doesn't break your workflows (JetBrains confirms it won't), and treat the 8.5% savings as a small bonus rather than a game-changer. Combine it with other cost-saving strategies like the Bash hooks and guardrails covered in our recent articles for meaningful savings. The key workflow change: stop chasing advertised token savings numbers and start measuring your actual agentic token usage. JetBrains' methodology — forced activation and A/B testing — is the gold standard. Run your own benchmarks with `claude code --measure-tokens` to see what actually works for your codebase.
This story is part of
Claude Code's Campus Conquest Flips Anthropic's Talent Pipeline, Leaving Google's Academic Edge in Doubt
Viral adoption at MIT and Stanford transforms Claude Code from product into recruiting funnel, threatening Google's long-held research talent dominance
Compare side-by-side
Claude Code vs Caveman
Enjoyed this article?
Share:

AI Toolslive

Five one-click lenses on this article. Cached for 24h.

Pick a tool above to generate an instant lens on this article.

Related Articles

From the lab

The framework underneath this story

Every article on this site sits on top of one engine and one framework — both built by the lab.

More in Opinion & Analysis

View all