genshijin-stats

You can check real token usage in a Claude Code session by triggering the /genshijin-stats command, which reads directly from session logs to display actual token consumption and estimated savings without relying on AI estimation.

Yes, you can compare token costs before and after prompt tuning by running the stats command across iterations, which evaluates compression-mode comparisons and provides cost feedback across your chat time window.

No, the token savings report does not rely on model guesswork because it reads actual token usage data directly from the Claude Code session logs, ensuring accurate cost feedback while the model performs no numeric computation.

The best way to view lifetime token savings for Claude Code is by using the session analytics command, which supports lifetime aggregation with optional time windows to track cost optimization across multiple sessions.

You can share your Claude Code session analytics summary by triggering the reporting hook, which generates preformatted stats with a one-line sharing format that highlights real token usage and estimated reductions.