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 instructions/juliusbrussee/caveman-code/claude-mdgit clone --depth 1 https://github.com/JuliusBrussee/caveman-codeWrote 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/instructions/juliusbrussee/caveman-code/claude-md)<a href="https://agentmods.dev/instructions/juliusbrussee/caveman-code/claude-md"><img src="https://agentmods.dev/badge/instructions/juliusbrussee/caveman-code/claude-md.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.00957 | $0.00957 |
| Opus 5 | $0.00478 | $0.00478 |
| Sonnet 5 | $0.00191 | $0.00191 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
caveman-code CLAUDE.md 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 4d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CAVE CLI — caveman-cli
Minimal terminal coding agent + multi-provider LLM toolkit. TypeScript monorepo.
Packages
| Package | CLI | Purpose |
|---|---|---|
| v2 core (load-bearing): | ||
packages/coding-agent |
caveman |
Coding agent: sessions, extensions, skills, themes, slash commands, subagents |
packages/ai |
pi-ai |
Unified LLM API: OpenAI, Anthropic, Google, more |
packages/agent |
— | Agent runtime: tool calling, loop, state, system-prompt/toolFilter/maxTurns |
packages/tui |
— | Terminal UI: differential rendering, chord input, notifications |
packages/sdk |
— | @juliusbrussee/caveman-sdk — TS client for caveman-code daemon HTTP+WS API (openapi-generated) |
packages/markdown-preview |
— | Markdown renderer used by TUI |
Out of scope for v2 (separate product surfaces, kept independent):
| packages/web-ui | — | Web components for AI chat |
| packages/mom | mom | Slack bot → delegates to coding agent |
| packages/pods | cave-pods | vLLM deployment on GPU pods |
Key Commands
npm install # install all deps
npm run build # build all packages
npm run lint # biome lint
npm run format # biome format
Context Hierarchy
See context/CLAUDE.md. The active plan is context/plans/cave-v2-best-in-class.md.
Legacy CaveKit kits/plans/impl have been moved to context/archive/.
Conventions
- Biome for lint/format (not ESLint/Prettier). Config:
biome.json. - TypeScript strict. Shared tsconfig:
tsconfig.base.json. - Package scope:
@juliusbrussee/caveman-*(all packages on npm). Main CLI package:@juliusbrussee/caveman-code. Bin registerscavemanANDcaveman-codealiases. - Node.js 20+.
Current State (2026-05-01)
- No permission system. Sandbox/permissions/approval-prompts stripped on
branch
strip/permissions. Caveman Code runs autopilot. Don't reintroduce. See memoryfeedback_no_permissions. - Plan mode wired.
/planenters read-only chat mode (no edits, no shell writes);/actexits. Slash command atpackages/coding-agent/src/core/slash-commands/plan.ts. Plan-mode gating also enforced inside the Task tool for spawned subagents. - Subagents. Registry +
SendMessagetool in coding-agent. Subagent isolation honored by Task tool. Agent definitions usetoolconstraints instead of removedpermissionModefrontmatter. - AgentSession features: checkpoints, repomap, chat mode, soft compaction,
hooks, MCP, skills, recipes,
/clear,/quick-open,/task-list. - Goal loop (in-flight, untracked):
packages/coding-agent/src/core/goal-loop/—goal-runner,goal-state,goal-prompts. Not yet committed; dev work onstrip/permissions. - Walkthrough doc:
context/notes/agent-loop-walkthrough.mdtraces the full path fromcavemanboot →interactive-modedispatch →session.prompt→agent-loop.runLoop. Read this first when touching the loop.
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.
- 4d ago First seen · 74 lines · 957 tokens per session scan A 7dd3b9f66c12
caveman-code CLAUDE.md is an instructions file published in the GitHub repository JuliusBrussee/caveman-code (930 stars, last pushed 20d ago), licensed MIT. It adds 957 tokens to every session, about $0.0048 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.