From caveman
Show real token usage and estimated savings for the current session. Reads directly from the Claude Code session log — no AI estimation. Triggers on /caveman-stats. Output is injected by the mode-tracker hook; the model itself does not compute the numbers.
How this skill is triggered — by the user, by Claude, or both
Slash command
/caveman:caveman-statsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill is delivered by `hooks/caveman-stats.js` (read by `hooks/caveman-mode-tracker.js` on `/caveman-stats`). The model does not need to do anything when this skill fires — the hook returns `decision: "block"` with the formatted stats as the reason. The user sees the numbers immediately.
This skill is delivered by hooks/caveman-stats.js (read by hooks/caveman-mode-tracker.js on /caveman-stats). The model does not need to do anything when this skill fires — the hook returns decision: "block" with the formatted stats as the reason. The user sees the numbers immediately.
npx claudepluginhub ptlnextdoor/crackstack --plugin cavemanGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.