Input Token Analysis

Explain aggregate input token consumption. Answer three questions with numbers: where did the tokens go, which consumers dominate, what config or prompt change reduces them. Distinct from input-token-overheads, which audits per-turn system-prompt blocks. This skill audits total volume across sessions, cron fires, and tool traffic.

When to Use

• Monthly/weekly input token bill is large and unexplained (e.g. "2.4B tokens in 30 days")
• After applying token-saving changes — measure the delta against a baseline
• A cron job is suspected of runaway token use

For per-turn context-window health, use input-token-overheads. For API billing disputes, use the provider's usage dashboard — local telemetry cannot see provider-side caching.

Quick Start

Run the audit script (read-only, pure stdlib):