caveman-stats

Reports actual session token usage and estimated savings from the Claude Code session log.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/Sambhav242005/Major-Project --skill caveman-stats-sambhav242005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman-stats
Source: https://github.com/Sambhav242005/Major-Project/tree/main/.continue/skills/caveman-stats
Command: npx skills add https://github.com/Sambhav242005/Major-Project --skill caveman-stats-sambhav242005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Token-saving prompt modes often claim savings without evidence, leaving users unable to tell whether the mode actually helped or cost more than it saved. This Skill reads the real session log and reports measured input/output tokens, estimated savings, rule overhead, and net impact. ## Core Features & Use Cases - Real token receipts: Reads the JSONL session log on disk directly, so numbers come from recorded usage rather than model estimation. - Net savings accounting: Computes estimated rule overhead (default 1,250 input tokens per turn, configurable via CAVEMAN_RULE_OVERHEAD_TOKENS) and subtracts it from gross savings, flagging net-negative sessions plainly. - Statusline badge support: Writes a lifetime-savings suffix file consumed by the statusline badge for a glanceable gross-savings summary. - Use Case: After a long coding session in caveman mode, run /caveman-stats to see whether the output-token savings actually exceeded the input-token cost of the injected rules for that workload. ## Quick Start Type /caveman-stats in the session to display the current session's measured token usage, estimated savings, rule overhead, and net result.

Frequently Asked Questions about caveman-stats

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check token usage for the current Claude Code session?

Run /caveman-stats in the session. The mode-tracker hook intercepts the command, reads the JSONL session log on disk, and returns formatted input/output token counts plus estimated savings as a blocked-decision reason.

How are the token savings numbers calculated?

Savings compare measured caveman output tokens against an estimated non-caveman baseline derived from the session log. The model itself never computes the numbers; the hook reads recorded usage directly from disk.

What is the rule overhead line in the stats output?

Rule overhead estimates the per-turn input-token cost of the injected caveman rules, defaulting to 1,250 tokens per turn multiplied by the turn count. Override the default by setting the CAVEMAN_RULE_OVERHEAD_TOKENS environment variable.

Why does the net savings line sometimes show a negative number?

On short sessions with terse replies, output-token savings can be smaller than the input-token cost of injecting the rules every turn. The output states this net-negative result directly and suggests turning caveman off for that workload.

Can I see lifetime savings instead of per-session stats?

Each run writes a lifetime-savings suffix file that the statusline badge displays as a gross-savings figure. For the full net accounting, run /caveman-stats rather than relying on the badge.