Cost per Conversation
cost-report and cost-optimize aggregate by agent and model. This skill aggregates by conversation (session) — a different lens that surfaces which conversations cost the most. Useful for retrospectives ("which sessions ran long on Opus?") and for evaluating whether a given project's session pattern is sustainable.
When to use
- After multiple sessions, to see total spend per conversation.
- Before scoping a long session, to understand typical cost-per-conversation.
- For per-project rollups via
CONV_NAMESPACE=cost-tracking-<project>.
Steps
Run the script from anywhere:
node plugins/ruflo-cost-tracker/scripts/conversation.mjsOptional env:
CONV_FORMAT=json— emit JSON instead of markdownCONV_LIMIT=20— show only the most recent N conversationsCONV_NAMESPACE=cost-tracking— override target namespace
Inspect the markdown table — total cost across all conversations, per-tier rollup, then a per-session table (started-at, sessionId prefix, message count, top model, cost).
Cross-references
cost-track— the producer that populatescost-tracking:session-*cost-report— same data, per-agent / per-model lenscost-trend— drift across bench runs (different axis: corpus runs vs conversations)cost-budget-check— sums across conversations to evaluate the budget threshold