🐙
Freeclaude codetokenscostskillsefficiencyopen source

Caveman is a Claude Code skill with one brilliant trick: it instructs the model to communicate internally using stripped-down caveman-style language, slashing token consumption by up to 65% without meaningfully degrading output quality. It is especially useful for long agentic sessions where token costs accumulate rapidly. With over 76,000 GitHub stars it is one of the most widely adopted cost-reduction tools in the Claude Code ecosystem.

What is Caveman?

Caveman is a Claude Code skill built around one idea: instruct the model to communicate in stripped down, telegraphic language rather than full prose, and the token count of a long session drops. Articles, filler and conversational padding go away, and what remains is the content that actually carries meaning. The project claims a substantial reduction in token consumption without a meaningful loss in the quality of the work produced. Installation is the ordinary skill workflow, meaning you drop it into your agent's configuration rather than running a service. It is a small, single purpose piece of the Claude Code ecosystem, which is worth saying plainly. There is no dashboard, no accounting and no per task analysis. It changes how the assistant writes, and the saving comes from that alone. Whether the tradeoff suits you depends heavily on what you use the output for.

Who is Caveman for?

The situation this fits is a long agentic session where the assistant is generating a great deal of intermediate text that nobody reads closely. Extended refactors, repository wide sweeps, iterative debugging loops, anything where the model narrates as it goes. In that setting the prose is overhead, and compressing it is close to free. It fits worst where the writing is the deliverable. If you are producing documentation, commit messages, code comments or anything a colleague will read, terse shorthand is a downgrade, not a saving. A reasonable pattern is to enable it for grinding work and turn it off when the session shifts to writing something for humans. Try it on a session you can afford to redo before trusting it on work that matters.

How does Caveman compare?

SkillOpt sits in the same corner of this category, concerned with making agent skills themselves leaner rather than changing how the assistant speaks, so the two address different parts of the same budget. Repomix attacks the input side instead, packing a repository into a single structured file so the agent reads your code efficiently, which for most projects is where the tokens actually go. Claude Mem is about not repeating yourself across sessions, compressing what happened and reinjecting only what is relevant later. Caveman is the narrowest and the cheapest to try of the four, because enabling it changes one behavior and you can judge the result in a single session.

Compare with: SkillOpt, Repomix, Claude Mem

Caveman pricing

The catalog records this as free. It is an open source skill, a set of instructions rather than software you run, so there is no install cost and nothing to host. Its entire point is reducing a cost you already pay, namely the tokens your agent consumes during long sessions. Savings depend on how you work, so treat the project's claims as a reason to test rather than a number to budget against. Measure your own usage before and after on comparable work.

Notes

No notes have been added for this tool yet.

Caveman FAQ

Does Caveman make the code worse?
It changes how the assistant writes prose, not how it writes code. The project's position is that output quality holds while token use falls. The honest answer is to test it on your own work, because reasoning that happens in text can be affected by compressing that text, and how much depends on the task.
How much does it actually save?
That varies with your workflow, and no single figure transfers between users. Sessions full of narration and long explanations have more to compress than short, tightly scoped tasks. Run a comparable piece of work with it on and off and compare your own usage, which is the only measurement that reflects your setup.
Can I turn it off for some tasks?
Yes, and you probably should. It is a skill, so it is enabled or disabled like any other. Keep it on for long grinding sessions where intermediate text is throwaway, and off when the writing is the deliverable, such as documentation, commit messages or anything another person will read carefully.
Browse all Open Source