cavecrew

cavecrew is a skill for Claude Code from JuliusBrussee/caveman. It costs 65 tokens per session (944 once invoked), scanned A, original, Apache-2.0.

A coordinator for choosing among specialised coding agents: one for locating code, one for small edits, and one for reviewing changes. It sends work to the suitable agent instead of handling every task directly.

In plain words
What is it for?
Use it when deciding whether to locate code, make a bounded one- or two-file change, or review a diff.
Why use it?
It keeps each task focused and reduces the amount of detail that must remain in the main conversation.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Part of the caveman plugin — 22 skills, 9 commands, 3 agents shipped together

Good fit Use it when deciding whether to locate code, make a bounded one- or two-file change, or review a diff.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/juliusbrussee/caveman/cavecrew
About the project

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.

JuliusBrussee/caveman · 113,062 stars · on GitHub · docs.caveman.so

Install

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.

Any agent
npx skills add JuliusBrussee/caveman --skill cavecrew
Clone the repo
git clone --depth 1 https://github.com/JuliusBrussee/caveman

Made for: Claude Code.

Or install caveman, the plugin that ships this one along with the rest of its 22 skills, 9 commands, 3 agents.

Wrote 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.

agentmods badge for cavecrew

README.md
[![agentmods](https://agentmods.dev/badge/skills/juliusbrussee/caveman/cavecrew/github.svg)](https://agentmods.dev/skills/juliusbrussee/caveman/cavecrew)
Your own site
<a href="https://agentmods.dev/skills/juliusbrussee/caveman/cavecrew"><img src="https://agentmods.dev/badge/skills/juliusbrussee/caveman/cavecrew/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.

agentmods 80×15 button for cavecrew

Your own site · 80×15
<a href="https://agentmods.dev/skills/juliusbrussee/caveman/cavecrew"><img src="https://agentmods.dev/badge/skills/juliusbrussee/caveman/cavecrew.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 944 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 9 Oct 2026
  • Snyk pass 9 Oct 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00065 $0.00944
Opus 5.5 $0.00026 $0.00378
Sonnet 5.5 $0.00013 $0.00189
Haiku 4.5 $0.00006 $0.00094

Measured 8d ago against content hash 534c0a70d4c7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cavecrew 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 8d 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

  • cavecrew — 100% identical, 10 lines differ
  • cavecrew — 92% identical, 12 lines differ
plugins/caveman/skills/cavecrew/SKILL.md · 78 lines

How it starts

The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cavecrew = three subagent presets that answer in ultracave voice (tool runs: one status line in, one out; nothing between routine calls). Same job as Anthropic defaults (Explore, edit-style agents, reviewer); difference is the tool-result they return is compressed, so main context shrinks per delegation.

When to use cavecrew vs alternatives

Task Use
"Where is X defined / what calls Y / list uses of Z" cavecrew-investigator
Same but you also want suggestions/architecture commentary Explore (vanilla)
Surgical edit, ≤2 files, scope obvious cavecrew-builder
New feature / 3+ files / cross-cutting refactor Main thread, or feature-dev:code-architect if installed
Review diff, branch, or file for bugs cavecrew-reviewer
Deep code review with rationale + alternatives Code Reviewer (vanilla) if installed, else main thread
One-line answer you already know Main thread, no subagent

Rule of thumb: if you'd want the subagent's output in 1/3 the tokens, pick cavecrew. If you'd want prose, pick vanilla.

Why this exists (the real win)

Subagent tool results get injected into main context verbatim. A vanilla Explore that returns 2k tokens of prose costs 2k tokens of main-context budget every time. The same finding from cavecrew-investigator comes back as a compressed path:line table instead. Across 20 delegations in one session that's the difference between context exhaustion and finishing the task.

Output contracts

What main thread can rely on per agent:

cavecrew-investigator

<Header>:
- path:line — `symbol` — short note
totals: <counts>.

Or No match. Always file-path-first, line-number-attached, backticked symbols. Safe to grep with path:\d+.

cavecrew-builder

<path:line-range> — <change ≤10 words>.
verified: <re-read OK | mismatch @ path:line>.

Or one of: too-big. / needs-confirm. / ambiguous. / regressed. (terminal first token).

cavecrew-reviewer

path:line: <emoji> <severity>: <problem>. <fix>.
totals: N🔴 N🟡 N🔵 N❓

Or No issues. Findings sorted file → line ascending.

Read the full file on GitHub · 78 lines

Changes

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.

  1. 8d ago Changed 534c0a70d4c7
  2. 14d ago Changed d8a21355e717
  3. 1mo ago First seen · 78 lines · 65 tokens per session scan A c05f8e8d16bd

Subscribe to this mod's changes

cavecrew is a skill published in the GitHub repository JuliusBrussee/caveman (113,062 stars, last pushed 2d ago), licensed Apache-2.0. It adds 65 tokens to every session and 944 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.