Skip to content
Code Recycle
Free · open sourceApache-2.0Unclaimed listing

caveman is by JuliusBrussee — not by us.

We indexed this project so people can find it. We are not selling it, we host no copy of the code, and we are not affiliated with or endorsed by its authors — get it from them.

Indexed Oct 5, 2026 · 109,927 stars at index time. Maintainers: claiming verifies your identity and unlocks a higher assurance tier. Removal requests are honored.

Application · for humans & their agents

caveman

unclaimed listingactively maintainedFreeApache-2.0

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

by Open Source Community · New publisher

Go to the project ↗Open live demo ↗

Every claim on this page is refundable if it is untrue — refund policy.

docs.caveman.so/docs/quickstart

JuliusBrussee/caveman is an open-source project by JuliusBrussee: 🪨 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.. Indexed here so it can be found — not resold.

It is free. Get it from the upstream repository: https://github.com/JuliusBrussee/caveman

From the project's own README (excerpt, reproduced for discovery under its Apache-2.0 license):

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 through the proxy 54 Claude Code runs, 18 of 18 answers right 129.8× smaller web pages for the agent caveman browse vs a Playwright snapshot 1.4 to 2.4× cheaper with caveman-style output Adobe Research , eight models

Cited by Adobe Research · A/B tested by JetBrains · Remade for Elasticsearch on Elasticsearch Labs #1 on Hacker News · #1 on GitHub Trending · "No way this actually works." ThePrimeagen

How it talks · Install · The numbers · The proxy · What you get · In the wild

---

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.

Pick your club:

Skill Same answer Tokens --- --- ---: /caveman New object ref each render, so React re-renders. Wrap the prop in useMemo. 20 /ultracave Inline object prop, new ref, re-render. useMemo. 14 /megacave 新參照致重繪。useMemo。 13

Token counts: tiktoken o200k.

How caveman talks

Caveman is a voice, not broken grammar. Every reply follows the same structure:

Rule What it means --- --- Answer first [thing] [action] [reason]. [next step]. No greeting, no "let me", no recap, no "hope this helps" One idea per sentence Built on ASD-STE100, the controlled English written for aircraft…

Preview

See what it does before you commit. Previews show behavior, never source code.

01Capabilities

Does

  • No capabilities recorded

Doesn’t

  • No exclusions declared

02Requirements & stack

Depends on

No declared dependencies

Credentials needed

None declared

Stack

go

03Community

No endorsements yet

No verified confirmations yet — be the first.

Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.

Open an issue

Sign in to confirm — weight comes from verified usage, not vote count.

Nobody has reported anything yet — a success counts as a report too.

04Trust Passport

Full passport →
–/100

0/0 automated components pass. An automated score is never a security guarantee.

This listing is unclaimed, so publisher identity cannot be verified and it stays below the “verified” tier by design — that is a statement about the listing, not about the project’s quality. Our automated scans still ran; a maintainer who claims it unlocks identity verification.

VersionChannelReleasedNotes
0.0.0stableOct 5, 2026Indexed listing — see the upstream repository for real release history.