token-report

Analyze compaction-debugger logs to quantify token savings per session.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Lsogod/compaction-debugger --skill token-report-lsogod
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: token-report
Source: https://github.com/Lsogod/compaction-debugger/tree/main/skills/token-report
Command: npx skills add https://github.com/Lsogod/compaction-debugger --skill token-report-lsogod

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill collects and explains how token usage changes across compaction-debugger rounds, helping users quantify and reason about token savings.

Core Features & Use Cases

  • Compute per-round original and preprocessed token estimates, and actual savings.
  • Generate explanations of savings sources and identify trends across sessions.
  • Use in audits to communicate efficiency improvements to stakeholders.

Quick Start

Run the token-report to generate the latest per-session token savings summary from logs.

Frequently Asked Questions about token-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I quantify token savings from compaction-debugger logs across sessions?

To quantify token savings from compaction-debugger logs, parse fields like sourceEstimatedTokens and estimatedTokens to generate per-round and per-session insights, calculating original estimates, preprocessed estimates, and actual savings.

What is the best way to analyze token usage trends in long conversations with many rounds?

Analyzing token usage trends in long conversations involves applying pre-processing to affect token usage and identifying savings sources across sessions. This helps users reason about efficiency improvements and communicate them during audits.

Can I generate a per-session token savings summary directly from logs directory access?

Yes, you can generate a per-session token savings summary directly from the logs directory. The process requires access to the logs directory and the ability to parse specific fields like estimatedTokenSavings to produce the latest insights.

Does token reporting explain where the savings come from during pre-processing?

Token reporting does explain where savings come from during pre-processing by generating explanations of savings sources. It identifies trends across sessions and helps communicate these efficiency improvements to stakeholders.

When do I need to run a token report for my conversation logs?

You need to run a token report for conversation logs when you have long conversations with many rounds where pre-processing affects token usage. It is specifically used when users want to understand savings trends and quantify efficiency.