token-dashboard

Token Dashboard

Show read-only token telemetry for the current session and current UTC calendar week. The week starts Monday at 00:00 UTC. This skill has no /usage alias and does not modify transcripts or settings.

Usage

/token-dashboard                    # terminal dashboard; optional OpenRouter analytics when configured
/token-dashboard --offline          # local telemetry only; guarantees no network
/token-dashboard --json             # normalized schema v1 JSON
/token-dashboard --json --offline   # machine-readable local-only report
/token-dashboard --session-id ID    # explicitly select a known local session; the ID is never emitted

Resolve scripts/token_dashboard.py relative to this SKILL.md, then run the executable with the user's arguments. Pi can load the managed Claude/Codex skill directory through its configured skills path, and the collector remains compatible with Pi telemetry:

/path/to/token-dashboard/scripts/token_dashboard.py --offline
/path/to/token-dashboard/scripts/token_dashboard.py --json

Do not replace the collector with ad-hoc transcript reads or provider calls. Never call this skill /usage.

Output contract

The final response must paste the collector's complete stdout verbatim in a fenced code block. Do this even when the Bash tool card already contains the same output or Pi collapses earlier lines. Do not summarize, paraphrase, reformat, truncate, or replace stdout with a success message. Preserve all Current session, Week, and Sources rows, including unavailable and partial diagnostics. Use a json fence for --json and a plain-text fence otherwise. Do not alter the block itself.

Analysis contract

After the verbatim block, add an Analysis section of two to four concise bullets (at most 120 words total):

• summarize current-session requests and recorded total; when both counters are available, identify cache-read share as telemetry rather than cost;
• identify the largest week-to-date rows whose total is available, without treating rows with an unavailable total as zero;
• explain partial, estimated, or unavailable data using the reported source diagnostics; and
• mention one actionable setup issue, such as a missing OpenRouter management key, only when present.