mcpField
C
cost-conversation

cost-conversation

github.com/ruvnetAgent workflows80.0k682 installsUpdated today
Repository

About cost-conversation

Cost per Conversation is an agent skill for reviewing cost-tracking data by conversation rather than by agent or model. It helps teams compare session spending, examine expensive sessions, and assess project-level patterns.

Key features

  1. 01Conversation-level cost totals
  2. 02Per-tier cost rollups
  3. 03Per-session model and message details
  4. 04Markdown or JSON output
  5. 05Recent-session limit and namespace override

Use cases

  1. 01Review spending after multiple sessions
  2. 02Estimate typical cost before a long session
  3. 03Compare conversation costs within a project

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ruvnet/ruflo --skill cost-conversation

After installing, type/cost-conversationin Claude Code to confirm it loaded.

Details

From the project README

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.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 / per-model lens
  • cost-trend — drift across bench runs (different axis: corpus runs vs conversations)
  • cost-budget-check — sums across conversations to evaluate the budget threshold

Comments

Markdown supported