---
name: Receipts
slug: receipts
category: Data
description: Receipts shows a personal model-quality trend card for recent Claude Code sessions. Use it to review failure rate, edit churn, and tokens per task by model version and call out any shifts.
github: "https://github.com/karanb192/claude-code-hooks/tree/main/plugins/nerf-receipts/skills/receipts"
language: JavaScript
stars: 486
forks: 34
install: "npx degit https://github.com/karanb192/claude-code-hooks/tree/main/plugins/nerf-receipts/skills/receipts ~/.claude/skills/receipts"
installs_to: ~/.claude/skills/receipts
source_path: plugins/nerf-receipts/skills/receipts/SKILL.md
collection_size: 7
category_size: 668
collection_url: "https://dirskills.com/collections/karanb192/claude-code-hooks"
added: 2026-08-26T05:13:22.028Z
last_synced: 2026-08-26T05:13:22.028Z
canonical_url: "https://dirskills.com/skills/receipts"
---

# Receipts

Receipts shows a personal model-quality trend card for recent Claude Code sessions. Use it to review failure rate, edit churn, and tokens per task by model version and call out any shifts.

**Install:**

```bash
npx degit https://github.com/karanb192/claude-code-hooks/tree/main/plugins/nerf-receipts/skills/receipts ~/.claude/skills/receipts
```

## README

# Nerf receipts: your model-quality trend card

!`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.