Expose session token usage and spend via an MCP tool or context injection

まず、既存の /context および /usage スラッシュコマンドのエントリポイントを追跡し、セッション トークン、コンテキストウィンドウ、クレジット、支出メトリクスがどこで計算されているかを確認します。~/.commandcode/projects/*.jsonl にあるセッションのトランスクリプトと history.jsonl を調査し、現在どのメタデータが永続化されているかを確認します。1 つの実装方針を定め、モデルがユーザーによるコピー＆ペーストなしで、現在のセッションの正確な使用量と USD 建ての支出を取得できることを検証します。

Feature Description

The current session's token usage and spend in USD are only accessible via the /context and /usage slash commands, which require manual user input. There is no way for the model (agent) to programmatically read these metrics within a session. I propose exposing this data through one of:

1. An MCP tool the model can call (e.g. get_session_usage) that returns token count, context window percentage, credits used, and spend in USD.
2. Injecting the data into the session context (system prompt or environment variable) so it's always available to the model.
3. Persisting token cost alongside each message in session transcripts (~/.commandcode/projects/*.jsonl) so the model can compute it from the history.

This would enable building skills like a "session-insights" agent that answers "how many tokens have we used?" or "what's the spend so far?" on demand.

Use Case

I want to ask "how many tokens have we used in this session?" or "what's the bill so far in USD?" and get an instant answer without having to manually run slash commands and paste output. A skill that surfaces this data would be far more useful if the model can fetch it directly rather than asking the user to type /context and /usage.

Additional Context

The session transcript files (~/.commandcode/projects/users-*/.jsonl) store conversation text and basic metadata (timestamp, source) but no token counts or cost data. The history.jsonl file also lacks this. As a result, the model has zero visibility into usage metrics — it can only ask the user to run slash commands and interpret what they paste back.

How important is this to you?

Important for my workflow