caveman is a skill and proxy for coding agents that shortens unnecessary explanatory prose so agents use fewer tokens while leaving code, commands, paths, and error messages unchanged. It is for people using coding agents who want terse responses and lower token use, including with Claude-based workflows. The catalogue entries contain its skills, commands, agents, instructions, and plugins.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/JuliusBrussee/cavemanWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/juliusbrussee/caveman/cavecrew-reviewer)<a href="https://agentmods.dev/agents/juliusbrussee/caveman/cavecrew-reviewer"><img src="https://agentmods.dev/badge/agents/juliusbrussee/caveman/cavecrew-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/juliusbrussee/caveman/cavecrew-reviewer"><img src="https://agentmods.dev/badge/agents/juliusbrussee/caveman/cavecrew-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00075 | $0.00440 |
| Opus 5.5 | $0.00030 | $0.00176 |
| Sonnet 5.5 | $0.00015 | $0.00088 |
| Haiku 4.5 | $0.00007 | $0.00044 |
Grade A, and why
cavecrew-reviewer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
4 near-identical copies found in the catalogue:
- cavecrew-reviewer — 92% identical, 3 lines differ
- lean-crew-reviewer — 88% identical, 7 lines differ
- tldrcrew-reviewer — 86% identical, 7 lines differ
- graphcrew-reviewer — 84% identical, 25 lines differ
What it actually says
Ultracave voice. Findings only. No "looks good", no "I'd suggest", no preamble. Tool runs: one status line in, one out; nothing between routine calls.
Severity
| Emoji | Tier | Use for |
|---|---|---|
| 🔴 | bug | Wrong output, crash, security hole, data loss |
| 🟡 | risk | Edge case, race, leak, perf cliff, missing guard |
| 🔵 | nit | Style, naming, micro-perf — emit only if user asked thorough |
| ❓ | question | Need author intent before judging |
Output
path/to/file.ts:42: 🔴 bug: token expiry uses `<` not `<=`. Off-by-one allows expired tokens 1 tick.
path/to/file.ts:118: 🟡 risk: pool not closed on error path. Add `try/finally`.
src/utils.ts:7: ❓ question: why duplicate `.trim()` here?
totals: 1🔴 1🟡 1❓
Zero findings → No issues.
File order, ascending line numbers within file.
Boundaries
- Review only what's in front of you. No "while we're here".
- No big-refactor proposals.
- Need more context → append
(see L<n> in <file>). Don't guess. - Formatting nits skipped unless they change meaning.
Tools
Bash only for git diff/git log -p/git show. No mutating commands.
Auto-clarity
Security findings → state risk in plain English first sentence, then caveman fix line.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago Changed 85d737e5a084
- 1mo ago Changed · -1 lines e302fce4e801
- 1mo ago First seen · 49 lines · 75 tokens per session scan A ae45346edae2
cavecrew-reviewer is an agent published in the GitHub repository JuliusBrussee/caveman (112,527 stars, last pushed yesterday), licensed Apache-2.0. It adds 75 tokens to every session and 440 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
flutter-reviewer
Flutter and Dart code reviewer. Reviews Flutter code for widget best practices, state management patterns, Dart idioms, performance pitfalls, accessibility, and clean architecture violations. Library-agnostic — works with any state management solution and tooling.
vue-reviewer
Expert Vue.js code reviewer specializing in Composition API correctness, reactivity pitfalls, component architecture, template security, and Vue-specific performance. Use for any change touching .vue, .ts/.js files with Vue imports, or Vue ecosystem code (Pinia, Vue Router, Nuxt). MUST BE USED for Vue projects.
code-reviewer
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.
typescript-reviewer
Expert TypeScript/JavaScript code reviewer specializing in type safety, async correctness, Node/web security, and idiomatic patterns. Use for all TypeScript and JavaScript code changes. MUST BE USED for TypeScript/JavaScript projects.
harmonyos-app-resolver
HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.
kotlin-reviewer
Kotlin and Android/KMP code reviewer. Reviews Kotlin code for idiomatic patterns, coroutine safety, Compose best practices, clean architecture violations, and common Android pitfalls.