Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From hush
Reports how much hush's compression hook actually saved this session — a per-decision byte rollup from the HUSH_DEBUG manifest plus a per-model token breakdown from the transcript. Requires HUSH_DEBUG=1 to have been set during the work being measured; without it there is nothing to report.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hush:hush-stats [session-id]When to use
Trigger when the user asks how much hush saved, wants savings numbers for the current session, says "hush stats", "how much did hush save", "show hush's savings", or invokes /hush:stats.
[session-id]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Surfaces the value hush's compression hook already recorded but never showed anyone: a byte rollup of every decision it made this session, and — from the transcript itself — how many tokens each model actually used.
Surfaces the value hush's compression hook already recorded but never showed anyone: a byte rollup of every decision it made this session, and — from the transcript itself — how many tokens each model actually used.
node "${CLAUDE_PLUGIN_ROOT}/scripts/stats.js"
If the user gave a session id as an argument, pass it through: node "${CLAUDE_PLUGIN_ROOT}/scripts/stats.js" --session <id>.
The script auto-finds the current directory's most recent transcript when no id is given. It never modifies anything — read-only over the manifest and the transcript.
This means HUSH_DEBUG=1 wasn't set while the work being asked about happened — the manifest only exists when that flag was on (it's off by default; see the README's Settings table). Tell the user plainly: set HUSH_DEBUG=1 before the session (or turn) they want measured, then ask again. Do not estimate or infer savings from anything else — a guess dressed as a number is worse than admitting there's nothing to report.
State the outcome in plain sentences, not a wall of labels: total bytes saved (raw and net of hush's own one-time session note, if it fired), the one or two actions that did most of the work (e.g. "cap" or "sidecar"), and the per-model token counts if a transcript was found. Skip any section the script reported as unavailable rather than padding around it.
npx claudepluginhub v-songbird/hushShows real token usage and estimated savings for the current Claude Code session by reading the session log directly. Triggered via /caveman-stats.
Displays real token usage and estimated cost savings for the current Claude Code session by reading session logs directly. Invoke via /pordee-stats for accurate, non-AI computed stats.
Shows real token usage and estimated savings for the current Claude Code session by reading the session log directly.