A personal Claude Code impact report built from the session transcripts
already on disk at ~/.claude/projects, for the conversation where a dev
has to explain what their usage bought. Produces a markdown report and a
self-contained HTML receipt in the home directory.
Complements session-report, which reads the same transcripts to drive
usage down; this reads them to explain what the usage produced, and
cross-references local git history to tie spend to shipped work.
Two design rules the report is built around: no dollar figures, since a
cost inferred from local token counts won't match anyone's real bill and
inviting "that can't be right" discredits everything next to it; and no
invented "hours saved", since there's no baseline in local data to derive
a counterfactual from.
Mining is local — file I/O and git, no network. Tool calls are grouped
into five activity categories during mining so raw tool names, which
enumerate the dev's connected MCP servers, never leave the script. The
report is published nowhere unless the user asks.
