token-log

You can log token usage by running a command that appends input tokens, output tokens, and phase totals with a timestamp to a TOKEN-LOG.md file. This provides an auditable history of token consumption across designated story phases.

The best way to track cumulative token costs is by appending timestamped rows to a markdown log file after each phase. This maintains a running total across phases, ensuring consistent records for cost awareness and auditing.

Yes, token usage logging is designed to be invoked by workflow commands automatically after completing a phase. You pass the story identifier, phase label, and token counts to append a standardized record.

No external dependencies are required to maintain a token log. The process relies on simple file I/O to locate or create an implementation directory markdown file and append formatted text rows.

A limitation of tracking token usage in a markdown file is that records are append-only text rows without database querying capabilities. It is intended for simple auditing and cost awareness rather than complex data analysis.