token-report

Generate TOKEN-SUMMARY.md with token totals and cost estimates from TOKEN-LOG.md.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/michael-menard/monorepo --skill token-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: token-report
Source: https://github.com/michael-menard/monorepo/tree/main/.claude/skills/token-report
Command: npx skills add https://github.com/michael-menard/monorepo --skill token-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill reads a TOKEN-LOG.md and generates a TOKEN-SUMMARY.md with token totals and cost estimates.

Core Features & Use Cases

  • Read and parse TOKEN-LOG.md to extract per-phase token usage.
  • Generate a structured TOKEN-SUMMARY.md including inputs, outputs, totals, costs, and timelines.
  • Apply to a story identified by STORY-XXX under predefined plan directories (backlog, elaboration, ready-to-work, in-progress, QA, UAT).

Quick Start

Use the token-report command to generate a summary for a STORY-XXX by running /token-report STORY-XXX and ensuring a TOKEN-LOG.md exists at plans/stories/.../_implementation/TOKEN-LOG.md.

Frequently Asked Questions about token-report

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

FAQPage Schema
How do I generate a token usage summary and cost estimate for a story?

To generate a token usage summary, run the /token-report command with a STORY-XXX identifier. It parses your TOKEN-LOG.md to produce a TOKEN-SUMMARY.md with token totals and cost estimates.

What is the required directory structure for token log analysis?

Token log analysis requires a TOKEN-LOG.md file located at <story-directory>/_implementation. The story directory must follow the plans/stories/.../STORY-XXX path structure across designated directories like backlog or QA.

Can I estimate costs for stories across different workflow stages?

Yes, you can estimate costs for stories across various workflow stages. The tool operates on designated story directories including backlog, elaboration, ready-to-work, in-progress, QA, and UAT to produce per-story summaries.

How does the token cost estimation process work?

The token cost estimation process works by parsing each row in the TOKEN-LOG.md file to extract per-phase token usage. It then applies a defined cost model to calculate the final expense totals.

What should I do if my token usage summary is missing data?

If your token usage summary is missing data, verify that a TOKEN-LOG.md exists at plans/stories/.../_implementation. The generation process validates the presence of this file before parsing table rows for the report.

Do I need any external dependencies to run a token report?

No external dependencies are required to run a token report. The skill operates independently to read your TOKEN-LOG.md and generates a structured TOKEN-SUMMARY.md with inputs, outputs, and total costs.