From nerf-receipts
Show your personal model-quality trend card (failure rate, edit churn, tokens/task by model version)
How this skill is triggered — by the user, by Claude, or both
Slash command
/nerf-receipts:receiptsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
!`node "${CLAUDE_SKILL_DIR}/../../nerf-receipts.js" --render 2>/dev/null || node "${CLAUDE_PLUGIN_ROOT}/nerf-receipts.js" --render`
!node "${CLAUDE_SKILL_DIR}/../../nerf-receipts.js" --render 2>/dev/null || node "${CLAUDE_PLUGIN_ROOT}/nerf-receipts.js" --render
The card above is your own per-session flight recorder, aggregated across your recent
Claude Code sessions and keyed by model id and Claude Code version — failure rate, edit
churn, and tokens per task, each with a sparkline. It is recorded quietly in the background
by the nerf-receipts hooks as you work.
Briefly interpret it for the user: call out the headline averages, and if a ⚠ shift line is present, restate which metric moved, by how much, and across which model change — that is the receipt that a quality shift is real, not a vibe. If the card says data is still accumulating, tell them to keep working and check back after a few more sessions. Keep it short and do not re-run any commands.
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
npx claudepluginhub karanb192/claude-code-hooks --plugin nerf-receipts