What is caveman-code AGENTS.md?

A set of coding instructions for Caveman Code, covering how an agent should begin work, organize modules, write code, and handle GitHub issues. It also lists the project’s packages, such as the agent, terminal interface, and web UI.

Use it to orient yourself in the repository, choose the relevant package documentation, follow TypeScript and code-quality rules, configure key bindings correctly, and prepare changes for review.

It tells the agent what project information to read before starting and sets rules for safe, maintainable changes. This helps prevent guessed types, hidden key bindings, and removing code without checking its purpose.

How JuliusBrussee/caveman-code configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to JuliusBrussee/caveman-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/JuliusBrussee/caveman-code/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/JuliusBrussee/caveman-code

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/juliusbrussee/caveman-code/agents-md/github.svg)](https://agentmods.dev/instructions/juliusbrussee/caveman-code/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/juliusbrussee/caveman-code/agents-md"><img src="https://agentmods.dev/badge/instructions/juliusbrussee/caveman-code/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/juliusbrussee/caveman-code/agents-md"><img src="https://agentmods.dev/badge/instructions/juliusbrussee/caveman-code/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,819 This file is loaded in full into every session.

When invoked 2,819 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.02819	$0.02819
Opus 5.5	$0.01128	$0.01128
Sonnet 5.5	$0.00564	$0.00564
Haiku 4.5	$0.00282	$0.00282

Measured 2mo ago against content hash a7b28cc22b14, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

caveman-code AGENTS.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 2mo 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.

AGENTS.md · 241 lines

How it starts

The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Development Rules

First Message

If the user did not give you a concrete task in their first message, read README.md, then ask which module(s) to work on. Based on the answer, read the relevant README.md files in parallel.

packages/ai/README.md
packages/tui/README.md
packages/agent/README.md
packages/coding-agent/README.md
packages/mom/README.md
packages/pods/README.md
packages/web-ui/README.md

Code Quality

No any types unless absolutely necessary
Check node_modules for external API type definitions instead of guessing
NEVER use inline imports - no await import("./foo.js"), no import("pkg").Type in type positions, no dynamic imports for types. Always use standard top-level imports.
NEVER remove or downgrade code to fix type errors from outdated dependencies; upgrade the dependency instead
Always ask before removing functionality or code that appears to be intentional
Do not preserve backward compatibility unless the user explicitly asks for it
Never hardcode key checks with, eg. matchesKey(keyData, "ctrl+x"). All keybindings must be configurable. Add default to matching object (DEFAULT_EDITOR_KEYBINDINGS or DEFAULT_APP_KEYBINDINGS)

Commands

After code changes (not documentation changes): npm run check (get full output, no tail). Fix all errors, warnings, and infos before committing.
Note: npm run check does not run tests.
NEVER run: npm run dev, npm run build, npm test
Only run specific tests if user instructs: npx tsx ../../node_modules/vitest/dist/cli.js --run test/specific.test.ts
Run tests from the package root, not the repo root.
If you create or modify a test file, you MUST run that test file and iterate until it passes.
When writing tests, run them, identify issues in either the test or implementation, and iterate until fixed.
For packages/coding-agent/test/suite/, use test/suite/harness.ts plus the faux provider. Do not use real provider APIs, real API keys, or paid tokens.
Put issue-specific regressions under packages/coding-agent/test/suite/regressions/ and name them <issue-number>-<short-slug>.test.ts.
NEVER commit unless user asks

Read the full file on GitHub · 241 lines

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.

2mo ago First seen · 241 lines · 2,819 tokens per session scan A a7b28cc22b14

Subscribe to this mod's changes

caveman-code AGENTS.md is an instructions file published in the GitHub repository JuliusBrussee/caveman-code (947 stars, last pushed 2mo ago), licensed MIT. It adds 2,819 tokens to every session, about $0.0113 per session on Opus 5.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.

caveman-code AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
caveman-code AGENTS.mdJuliusBrussee/caveman-code	Instructions file	947	2mo ago	MIT	A	2,819	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

caveman-code: Instructions file for Codex