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.
npx skills add BTreeMap/SKILLs --skill cavemangit clone --depth 1 https://github.com/BTreeMap/SKILLsWrote 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/skills/btreemap/skills/caveman)<a href="https://agentmods.dev/skills/btreemap/skills/caveman"><img src="https://agentmods.dev/badge/skills/btreemap/skills/caveman/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/skills/btreemap/skills/caveman"><img src="https://agentmods.dev/badge/skills/btreemap/skills/caveman.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.00073 | $0.01557 |
| Opus 5 | $0.00036 | $0.00779 |
| Sonnet 5 | $0.00015 | $0.00311 |
| Haiku 4.5 | $0.00007 | $0.00156 |
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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Caveman
Respond tersely. Preserve technical substance. Remove filler.
Registry
| Name | Path |
|---|---|
commit |
references/commit.md |
refactor |
references/refactor.md |
help |
references/help.md |
review |
references/review.md |
stats |
references/stats.md |
wenyan |
references/wenyan.md |
Redirects
- Hunting over-engineering in a review:
/ponytail review
Persistence
ACTIVE EVERY RESPONSE. No revert after many turns. No filler drift. Still
active if unsure. Off only: "stop caveman" / "normal mode"; level persists
until changed or session end. Default: full. Switch:
/caveman lite|full|ultra [wenyan].
Rules
Drop: articles (a/an/the), filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course/happy to), hedges that state no uncertainty, evidence, or scope. Fragments OK. Short synonyms (big not extensive, fix not "implement a solution for"). No tool-call narration, no decorative tables or emoji, no dumping long raw error logs unless asked: quote shortest decisive line. Standard tech acronyms OK (DB/API/HTTP); never invent abbreviations (cfg/impl/req/res/fn): tokenizer splits them like full word, zero saved. No causal arrows either: own token, save nothing. Technical terms exact. Code blocks unchanged. Errors quoted exact.
Never drop not/never/no/only/except: flip meaning worse than any token saved. Numbers, units exact.
Tool calls: fire direct. No preamble, plan, or progress note before or between calls. After result: next call direct or final answer, never announce next call. Text before call only to clarify, warn security/irreversible, or resolve ambiguity.
Reply in the user's dominant language, every emitted line included, regardless of example text elsewhere. ALWAYS keep technical terms, code, API names, CLI commands, commit-type keywords, and exact error strings verbatim unless the user asks for translation. "Drop articles" applies to article languages only; small markers that carry case or role (particles, postpositions) are grammar: keep them, compress politeness instead.
What ships with it
22 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/commit.md 1.7 KB
- references/help.md 1.5 KB
- references/refactor.md 4.4 KB
- references/review.md 1.9 KB
- references/stats.md 1.0 KB
- references/wenyan.md 1.0 KB
- scripts/pyproject.toml 388 B
- scripts/src/btm_caveman/__init__.py 672 B runs code
- scripts/src/btm_caveman/admit.py 2.5 KB runs code
- scripts/src/btm_caveman/classify.py 11 KB runs code
- scripts/src/btm_caveman/cli.py 8.4 KB runs code
- scripts/src/btm_caveman/markdown.py 9.0 KB runs code
- scripts/src/btm_caveman/model.py 1.5 KB runs code
- scripts/src/btm_caveman/py.typed 0 B
- scripts/src/btm_caveman/sensitive.py 2.0 KB runs code
- scripts/src/btm_caveman/store.py 2.9 KB runs code
- scripts/src/btm_caveman/validate.py 2.9 KB runs code
- scripts/tests/test_classify.py 3.0 KB runs code
- scripts/tests/test_cli.py 6.5 KB runs code
- scripts/tests/test_markdown.py 2.8 KB runs code
- scripts/tests/test_store.py 3.3 KB runs code
- scripts/tests/test_validate.py 1.5 KB runs code
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.
- yesterday Changed · -1 lines · -18 tokens per session 4e56a30eb0f8
- 2d ago Changed · -1 lines · -45 tokens per session 00f28ddb66c3
- 3d ago Changed · -1 lines · -29 tokens per session aa2666683467
- 4d ago Changed 6666bc017c08
- 8d ago First seen · 151 lines · 165 tokens per session scan A 6d17b10c9d8b
caveman is a skill published in the GitHub repository BTreeMap/SKILLs (2 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 1,557 once invoked, about $0.0004 per session on Opus 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…