cost-conversation
Per-conversation cost view — list every session in cost-tracking with started-at, message count, top model, and total cost
Profile →npx skills add ruvnet/ruflo --skill cost-conversation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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: ```bash node plugins/ruflo-cost-tracker/scripts/conversation.mjs ``` Optional env: - `CONV_FORMAT=json` — emit JSON instead of markdown - `CONV_LIMIT=20` — show only the most recent N conversations - `CONV_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 populates `cost-tracking:session-*` - `cost-report` — same data, per-agent
- When to use
- Steps
- Cross-references
node plugins/ruflo-cost-tracker/scripts/conversation.mjs
What does the cost-conversation skill do?
Per-conversation cost view — list every session in cost-tracking with started-at, message count, top model, and total cost
How do I install it?
Run `npx skills add ruvnet/ruflo --skill cost-conversation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ruvnet/ruflo, a repository with 67,015 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.