Be brief beats caveman plugin in Claude Code compression benchmark

Max Taylor benchmarked the popular Claude Code compression plugin 'caveman' against a trivial baseline: prepending 'be brief.' to each prompt. The results are surprisingly flat — but reveal where the plugin actually delivers value.
Benchmark methodology
24 prompts across six categories (bug diagnosis, concept explanation, architecture tradeoffs, multi-step setup, security/destructive ops, error interpretation). Each prompt had a rubric with required key points, required terms, and forbidden claims. Five arms were tested: baseline (no instruction), 'be brief.', and caveman at three intensity levels (lite, full, ultra). All ran via claude -p on claude-opus-4-7. Responses were scored by claude-sonnet-4-6 against the rubric.
Quality results
All arms scored within 1.5% of each other:
- Baseline: 0.985
- Brief: 0.985
- Lite: 0.976
- Full: 0.975
- Ultra: 0.970
Every arm hit 100% of key points. Zero forbidden claims triggered across 120 responses. Compression did not drop substantive content.
Token counts
| Arm | Mean tokens |
|---|---|
| Baseline | 636 |
| Brief | 419 (34% cut) |
| Lite | 401 |
| Full | 404 |
| Ultra | 449 |
'Be brief.' cut tokens by 34% vs baseline. Caveman lite and full landed close to brief. Ultra, the strictest mode, produced the longest answers of the three — but the category split tells a different story.
The category split reveals caveman's design
On bug diagnosis, concept explanations, architecture tradeoffs, and error interpretation, ultra is shortest or tied. Compression works as advertised. On multi-step setup and security warnings, all caveman modes show higher token counts. The reason: caveman's 'Auto-Clarity' rule explicitly disables compression for safety warnings, irreversible actions, and multi-step sequences. The safety escape engages, and compression stops — by design.
So what is caveman actually for?
If 'be brief.' matches on tokens and quality, the plugin's value is structural:
- Consistent output shape — every response follows the same pattern, useful for downstream tooling or uniform session feel.
- Intensity dial — slash commands to switch lite/full/ultra mid-session.
- Persistence across long sessions — caveman re-injects its ruleset via
SessionStartandUserPromptSubmithooks to prevent drift (not tested in this single-shot benchmark).
The full dataset and harness are open source.
📖 Read the full source: HN AI Agents
👀 See Also

Testing MiniMax M2.7 via API on Three Real ML and Coding Workflows
A developer benchmarks MiniMax M2.7 against Claude Opus 4.7 on three real tasks: refactoring a PyTorch project, drafting Obsidian notes, and more. Key findings and setup included.

Multi-Agent Trading Council System Using GPT-5.1 and Claude 4.6
A developer built a multi-agent trading system using ZagiHQ for orchestration with three parallel data-gathering agents and three LLMs (GPT-5.1, Claude 4.6 Opus, Claude 4.6 Sonnet) that must agree on trades. The system filters out setups through disagreement and requires manual approval.

Sponsio: Deterministic Guard Rails for OpenClaw — Blocking 'Legal but Wrong' Tool Calls
Open-source tool that sits at the tool boundary, evaluating each call with temporal logic contracts (~0.14ms p50). Prevents agents from editing files outside the working directory, force-pushing, or running migrations against the wrong database.

Quick-Question Plugin Automates Unity Development with Claude Code
A developer has released quick-question, a macOS plugin for Unity 2021.3+ that automates compilation, testing, and cross-model code review when using Claude Code. The tool includes 20 slash commands and uses a 'Tribunal' pattern where Codex and Claude review each other's findings.