cost-audit

To audit token usage in a Claude transcript, invoke the /cost command to capture current session costs and identify optimization opportunities. The tool scans reads, duplicates, and large files to produce an actionable report.

Token waste in a Claude coding session refers to unnecessary token consumption caused by repeated file reads, duplicate data, and large files. Identifying these waste signals allows you to apply fixes like adding paths to .claudeignore.

You optimize Claude costs for large transcripts by scanning for common waste signals like unnecessary reads and large files. The tool then generates an actionable report suggesting practical fixes such as seeding a CLAUDE.md scaffold.

Yes, you can perform cost analysis on your current Claude session by invoking the /cost command. It captures input and output breakdowns and detects common waste signals directly from your active session context.

The primary limitation of auditing a Claude session transcript is that the analysis requires existing transcript context to function. Without an active session or large transcript history available, the tool cannot identify waste or suggest optimizations.