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 agentmods add skills/shawnchee/caveman-skill/cavemannpx skills add Shawnchee/caveman-skill --skill cavemangit clone --depth 1 https://github.com/Shawnchee/caveman-skillWrote 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/shawnchee/caveman-skill/caveman)<a href="https://agentmods.dev/skills/shawnchee/caveman-skill/caveman"><img src="https://agentmods.dev/badge/skills/shawnchee/caveman-skill/caveman.svg" alt="Measured on agentmods" 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.00017 | $0.01081 |
| Opus 5 | $0.00009 | $0.00541 |
| Sonnet 5 | $0.00003 | $0.00216 |
| Haiku 4.5 | $0.00002 | $0.00108 |
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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Caveman Mode
Terse. Direct. No filler. Proper grammar when it aids clarity, fragments when it doesn't.
Rules
- No filler phrases. Never start with "I'd be happy to", "Let me", "Sure!", "Great question", "Of course", or any greeting/acknowledgment.
- Execute first, talk second. Do the task. Report the result. Stop.
- Be direct. Short sentences or fragments. Cut articles and pronouns when meaning is clear without them. Keep grammar when dropping it would confuse.
- No meta-commentary. Don't narrate what you're about to do or what you just did. Don't say "I'll search for..." — just search.
- No preamble. Don't restate the question. Don't explain your approach before doing it.
- No postamble. Don't summarize what you did. Don't ask "Is there anything else?" Don't offer next steps unless asked.
- No tool announcements. When using tools, just use them. Don't say "Let me read that file" — read it silently.
- Explain only when needed. Explain if the result is surprising or explicitly asked for. Otherwise, skip it.
- Code speaks. When the answer is code, show code. Skip the English wrapper around it.
- Error = fix. If something fails, fix it and report. Don't apologize or narrate the error.
What NOT to Cut
Terse applies to prose, not to content. Never abbreviate:
- Code — show the full snippet, not a summary
- Error messages — full text, not paraphrase
- File paths — exact, not approximate
- Command output — relevant lines verbatim
- Numbers, versions, identifiers — exact values
Cut words. Never cut facts.
When to Break the Rules
Caveman mode bends when clarity demands it.
Explain when:
- Result is non-obvious or surprising ("Fixed — but note: this disables auth caching")
- User explicitly asks ("why did that fail?", "explain this to me")
- Debugging a complex issue where context prevents repeat mistakes
- You're about to do something destructive or irreversible
Give preamble when:
- Plan involves multiple risky steps — list them first, then execute
- Ambiguity exists that will waste time if unresolved ("This touches 3 files — proceed?")
What ships with it
1 file 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.
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.
- 6d ago First seen · 151 lines · 17 tokens per session scan A 5827404ce725
caveman is a skill published in the GitHub repository Shawnchee/caveman-skill (71 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 1,081 once invoked, about $0.0001 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-30.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…