caveman-stats

Parse local JSONL session logs to report token usage and session savings.

1|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/Tyler-R-Kendrick/slm-training --skill caveman-stats-tyler-r-kendrick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman-stats
Source: https://github.com/Tyler-R-Kendrick/slm-training/tree/main/.agents/skills/caveman-stats
Command: npx skills add https://github.com/Tyler-R-Kendrick/slm-training --skill caveman-stats-tyler-r-kendrick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the uncertainty of AI token estimation by providing precise, log-based reporting on actual input and output usage during a session.

Core Features & Use Cases

  • Real-time Token Auditing: Reads directly from the local Claude Code session log to provide exact usage numbers.
  • Savings Visualization: Calculates and displays the token savings achieved by using the caveman-mode-tracker hook compared to a standard baseline.
  • Use Case: Use this during a long coding session to monitor your token consumption and verify the efficiency gains of your current interaction mode.

Quick Start

Trigger the caveman-stats skill by typing the command /caveman-stats into your chat interface.

Frequently Asked Questions about caveman-stats

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

FAQPage Schema
How do I track real-time token usage in Claude Code sessions?

You can track real-time token usage by parsing local JSONL session logs. This skill reads directly from the active Claude Code session log to provide exact input and output token numbers for accurate performance monitoring.

What's the best way to calculate token savings during AI-assisted development?

Calculate token savings by comparing your current session's log data against a standard baseline. This skill computes the difference automatically, displaying the exact token savings achieved during your AI-assisted development interactions.

Do I need direct read access to session log files to monitor token consumption?

Yes, you need direct read access to the active local JSONL session log file. The skill parses these local logs deterministically to generate accurate usage reports without relying on external estimation methods.

Can I audit input and output tokens precisely instead of estimating them?

Yes, you can audit tokens precisely by reading local JSONL logs. This eliminates the uncertainty of AI token estimation by providing exact, log-based reporting on actual input and output usage during your coding sessions.

Why does my AI token estimation not match my actual session consumption?

AI token estimation often differs from actual consumption because it lacks log-level precision. By parsing local JSONL session logs directly, you get deterministic usage reports that reflect true input and output token metrics.

How do I trigger token usage metrics reporting in my chat interface?

Trigger the token usage metrics by typing the command /caveman-stats into your chat interface. This parses the active session log and immediately generates a deterministic report of your current token consumption and savings.