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/stevesolun/ctx/caveman-helpnpx skills add stevesolun/ctx --skill caveman-helpgit clone --depth 1 https://github.com/stevesolun/ctxWrote 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/stevesolun/ctx/caveman-help)<a href="https://agentmods.dev/skills/stevesolun/ctx/caveman-help"><img src="https://agentmods.dev/badge/skills/stevesolun/ctx/caveman-help.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 | $0.00056 | $0.00564 |
| Opus 5 | $0.00028 | $0.00282 |
| Sonnet 5 | $0.00011 | $0.00113 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
caveman-help 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 5d 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.
Copies of this mod
6 near-identical copies found in the catalogue:
- caveman-help — 100% identical, 2 lines differ
- caveman-help — 100% identical, 2 lines differ
- caveman-help — 100% identical, 0 lines differ
- caveman-help — 100% identical, 0 lines differ
- caveman-help — 100% identical, 36 lines differ
- caveman-help — 100% identical, 2 lines differ
What it actually says
Caveman Help
Display this reference card when invoked. One-shot — do NOT change mode, write flag files, or persist anything. Output in caveman style.
Modes
| Mode | Trigger | What change |
|---|---|---|
| Lite | /caveman lite |
Drop filler. Keep sentence structure. |
| Full | /caveman |
Drop articles, filler, pleasantries, hedging. Fragments OK. Default. |
| Ultra | /caveman ultra |
Extreme compression. Bare fragments. Tables over prose. |
| Wenyan-Lite | /caveman wenyan-lite |
Classical Chinese style, light compression. |
| Wenyan-Full | /caveman wenyan |
Full 文言文. Maximum classical terseness. |
| Wenyan-Ultra | /caveman wenyan-ultra |
Extreme. Ancient scholar on a budget. |
Mode stick until changed or session end.
Skills
| Skill | Trigger | What it do |
|---|---|---|
| caveman-commit | /caveman-commit |
Terse commit messages. Conventional Commits. ≤50 char subject. |
| caveman-review | /caveman-review |
One-line PR comments: L42: bug: user null. Add guard. |
| caveman-compress | /caveman-compress <file> |
Compress .md files to caveman prose. Saves ~46% input tokens. |
| caveman-help | /caveman-help |
This card. |
Deactivate
Say "stop caveman" or "normal mode". Resume anytime with /caveman.
Configure Default Mode
Default mode = full. Change it:
Environment variable (highest priority):
export CAVEMAN_DEFAULT_MODE=ultra
Config file (~/.config/caveman/config.json):
{ "defaultMode": "lite" }
Set "off" to disable auto-activation on session start. User can still activate manually with /caveman.
Resolution: env var > config file > full.
More
Full docs: https://github.com/JuliusBrussee/caveman
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.
- 5d ago First seen · 60 lines · 56 tokens per session scan A c7a1591ce2e2
caveman-help is a skill published in the GitHub repository stevesolun/ctx (583 stars, last pushed 4d ago), licensed MIT. It adds 56 tokens to every session and 564 once invoked, about $0.0003 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…