MANDATORY: Follow the complete shared lifecycle contract in ${CLAUDE_PLUGIN_ROOT}/skills/shared/run-lifecycle.md with declared skill report-tokens.

Report Tokens

MANDATORY: READ ENTIRE FILE before composing user-facing prose: ${CLAUDE_PLUGIN_ROOT}/skills/shared/readability-style.md.

Analyze token costs from synchronized larch run logs for the selected skill (--skill=design|implement|debate) in the current Git repository. The CLI syncs once, scans the unpacked cache, reads the skill-specific token report JSON files, prices each run through larch_core::report, prints a markdown analysis, writes a durable NDJSON cache snapshot, renders the trend chart, and optionally posts a GitHub [Implement Analysis Report], [Design Analysis Report], or [Debate Analysis Report] issue.

For --skill=implement, reports carry no workflow dimension and graph/per-day trend output aggregates all runs into one All runs series/table set. For --skill=design and --skill=debate, one aggregate report is generated. Debate run logs may record no vendor token legs; the report prices what is present and otherwise surfaces the existing empty-report gap. The filed issue intentionally omits raw per-issue JSON and actual-spend reconciliation unless LARCH_REPORT_TOKENS_POST_ACTUAL_SPEND=1 is set.

Rate overrides: set environment variables documented in docs/configuration-and-permissions.md before invoking.

Flags

Pass any of these after the skill name (for example, /report-tokens --skill implement --no-issue):