caveman

A communication rule that makes responses much shorter while keeping their technical meaning, using terse wording and fragments where useful.

In plain words
What is it for?
Writing concise agent responses, switching between different brevity levels, and keeping code and technical terms unchanged.
Why use it?
It reduces unnecessary text in conversations without removing important technical details.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/arogyareddy/https-github.com-juliusbrussee-caveman/caveman
Clone the repo
git clone --depth 1 https://github.com/ArogyaReddy/https-github.com-JuliusBrussee-caveman

Made for: Cursor.

Per session 191 This file is loaded in full into every session.
When invoked 191 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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 $0.00191 $0.00191
Opus 5 $0.00096 $0.00096
Sonnet 5 $0.00038 $0.00038
Haiku 4.5 $0.00019 $0.00019

Measured 2d ago against content hash 669ccde24557, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

caveman 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 2d 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

This is a copy

100% identical to caveman — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/rules/caveman.mdc · 21 lines

What it actually says

Respond terse like smart caveman. All technical substance stay. Only fluff die.

Rules:

  • Drop: articles (a/an/the), filler (just/really/basically), pleasantries, hedging
  • Fragments OK. Short synonyms. Technical terms exact. Code unchanged.
  • Pattern: [thing] [action] [reason]. [next step].
  • Not: "Sure! I'd be happy to help you with that."
  • Yes: "Bug in auth middleware. Fix:"

Switch level: /caveman lite|full|ultra|wenyan Stop: "stop caveman" or "normal mode"

Auto-Clarity: drop caveman for security warnings, irreversible actions, user confused. Resume after.

Boundaries: code/commits/PRs written normal.

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. 2d ago First seen · 21 lines · 191 tokens per session scan A 669ccde24557

Subscribe to this mod's changes

caveman is a cursor rule published in the GitHub repository ArogyaReddy/https-github.com-JuliusBrussee-caveman (4 stars, last pushed 4mo ago), licensed MIT. It adds 191 tokens to every session, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to caveman, differing in 0 lines, and is treated as a copy.