Cost Conversation
- 588 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
cost-conversation is a ruflo Claude Code skill that lists every agent session in cost-tracking with started-at, message count, top model, and total cost for developers auditing per-conversation LLM spend.
About
cost-conversation is a Productivity & Planning skill in ruvnet/ruflo that aggregates LLM costs by conversation session instead of by agent or model. While cost-report and cost-optimize summarize spend by agent and model, this skill surfaces which individual sessions cost the most, including started-at timestamps, message counts, top model used, and total session cost. Developers reach for cost-conversation after multiple agent sessions to retrospect on expensive Opus runs, evaluate project session patterns, or scope budget before starting a long conversation. It runs via Bash against the ruflo cost-tracking store and is useful for sustainability reviews of agent-assisted development workflows.
- cost-conversation
Cost Conversation by the numbers
- 588 all-time installs (skills.sh)
- +10 installs in the week ending Jul 26, 2026 (Skillselion tracking)
- Ranked #673 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill cost-conversationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 588 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
Which agent conversations cost the most?
Use cost-conversation for development tasks
Who is it for?
Developers running many Claude Code sessions who need per-conversation cost breakdowns for retrospectives and budget planning.
Skip if: Teams wanting only aggregate agent or model totals without session-level attribution.
When should I use this skill?
User asks which sessions cost the most, wants per-conversation spend, or needs a retrospective on agent session costs.
What you get
Per-session cost table with started-at, message count, top model, and total spend
- Per-session cost report
- Top model per conversation
- Message count summary
Files
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
1. 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
2. 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
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kFAQ
How is cost-conversation different from cost-report?
cost-conversation aggregates LLM spend by individual conversation session with started-at, message count, top model, and total cost. cost-report and cost-optimize group costs by agent and model instead of per-session attribution.
When should cost-conversation run?
cost-conversation runs after multiple agent sessions to identify which conversations cost the most, evaluate Opus usage patterns, or scope budget before starting a long development session.