Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →karanb192/receipts
Show your personal model-quality trend card (failure rate, edit churn, tokens/task by model version)
Passed 11 of 21 test cases with the skill, and 10 of 21 without it.
and 3 more in the full report
4 fixed8 passed either way8 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
I can see the rendered flight recorder trend card above. Should I execute additional node script commands to refresh or double-check the figures before giving a summary?
| Checked | Without skill | With skill |
|---|---|---|
| Provides the summary directly without executing additional commands. | Missed | Passed |
The instructions your model reads when the skill loads.
!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.
test cases passed, vs 10 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.