caveman-setup

caveman-setup is a skill for Claude Code from JuliusBrussee/caveman. It costs 44 tokens per session (2,835 once invoked), scanned A, original, Apache-2.0.

A setup guide for connecting a repository to the Caveman Cloud gateway, which measures requests made to language models.

In plain words
What is it for?
Use it to configure spend tracking and request measurement for an agent working in a repository.
Why use it?
It adds visibility into language-model usage and spending while keeping the agent’s behavior unchanged.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the caveman plugin — 22 skills, 9 commands, 3 agents shipped together

Good fit Use it to configure spend tracking and request measurement for an agent working in a repository.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/juliusbrussee/caveman/caveman-setup
About the project

caveman is a skill and proxy for coding agents that shortens unnecessary explanatory prose so agents use fewer tokens while leaving code, commands, paths, and error messages unchanged. It is for people using coding agents who want terse responses and lower token use, including with Claude-based workflows. The catalogue entries contain its skills, commands, agents, instructions, and plugins.

JuliusBrussee/caveman · 114,861 stars · on GitHub · docs.caveman.so

Install

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.

Any agent
npx skills add JuliusBrussee/caveman --skill caveman-setup
Clone the repo
git clone --depth 1 https://github.com/JuliusBrussee/caveman

Made for: Claude Code.

Or install caveman, the plugin that ships this one along with the rest of its 22 skills, 9 commands, 3 agents.

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.

agentmods badge for caveman-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/juliusbrussee/caveman/caveman-setup/github.svg)](https://agentmods.dev/skills/juliusbrussee/caveman/caveman-setup)
Your own site
<a href="https://agentmods.dev/skills/juliusbrussee/caveman/caveman-setup"><img src="https://agentmods.dev/badge/skills/juliusbrussee/caveman/caveman-setup/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.

agentmods 80×15 button for caveman-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/juliusbrussee/caveman/caveman-setup"><img src="https://agentmods.dev/badge/skills/juliusbrussee/caveman/caveman-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,835 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket warn 14 Sept 2026
  • Snyk pass 14 Sept 2026
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Data Exfiltration · line 153
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.02835
Opus 5.5 $0.00018 $0.01134
Sonnet 5.5 $0.00009 $0.00567
Haiku 4.5 $0.00004 $0.00283

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

Security

Grade A, and why

caveman-setup scanned grade A with 1 finding 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 1mo 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

cheapest path if it has a script for it, otherwise curl **on the path matching
Origin

Copies of this mod

3 near-identical copies found in the catalogue:

skills/caveman-setup/SKILL.md · 223 lines

How it starts

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

You are wiring this repository through the Caveman gateway. Caveman is a byte-preserving LLM proxy: in record mode it measures what your app sends and what it costs, and changes nothing else. Your job is a minimal, verified integration — not a refactor.

The prompt that sent you here provides four values. Refer to them as:

  • GATEWAY — the gateway base URL (e.g. https://gateway.caveman.so or http://127.0.0.1:8787)
  • CAVE_API_KEY — the gateway auth secret (treat like any API key: env var only, never committed, never printed in full)
  • PROVIDER_KEYS — stored (provider keys live encrypted in Caveman Cloud) or byok (this app sends its own provider key per request)
  • DASHBOARD — the dashboard base URL (e.g. https://app.caveman.so)

If any value is missing, stop and ask for it. Do not guess a URL or mint a key.

Rules (non-negotiable)

  1. Coherent integration. Wire every live LLM callsite through existing configuration and responsible seams. Touch each layer correctness requires. No drive-by refactors or formatting sweeps; add an abstraction only when it clarifies ownership or lowers lifecycle cost.
  2. Secrets stay in env vars. CAVE_API_KEY goes into the env file the repo already uses (.env, .env.local, …). If that file isn't gitignored, add it to .gitignore and say so. Never hardcode the key in source.
  3. Report only what you observed. The final report states the HTTP status and usage numbers from the real verification response — never assumed success. If verification fails, report the failure template instead.
  4. Record mode only. You are adding measurement. You do not enable any optimization, and you do not claim any savings — verified savings are $0 until an optimizer is explicitly turned on and passes its eval gate.
  5. Provider keys are not your business. With PROVIDER_KEYS: stored you never see one. With byok, the app's existing provider key stays exactly where it already is.

Step 1 — Find every live LLM callsite

Read the full file on GitHub · 223 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.

  1. 1mo ago First seen · 223 lines · 44 tokens per session scan A 42c8b8eeba19

Subscribe to this mod's changes

caveman-setup is a skill published in the GitHub repository JuliusBrussee/caveman (114,861 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 2,835 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.