While cost-report shows you spending by agent and model, this gives you the per-conversation view: which individual sessions burned through the most tokens. You run a Node script that reads from the cost-tracking namespace and get back a markdown table with session start time, message count, top model used, and total cost for each conversation. It's the retrospective lens you want when you need to answer "why did that Opus session cost $12" or figure out if your typical project sessions are staying under budget. Works anywhere you've got cost-track running, and you can scope it to a specific project namespace if you're tracking multiple workstreams.
npx skills add https://github.com/ruvnet/ruflo --skill cost-conversation