Skill Market

cost conversation

Per-conversation cost view — list every session in cost-tracking with started-at, message count, top model, and total cost

GitHub
githubcommunity
0.0
0 installs73.4K GitHub starsby ruvnet

Skill Introduction

Overview
Per-conversation cost view — list every session in cost-tracking with started-at, message count, top model, and total cost

Core value

Turns reusable Other know-how into an installable skill, helping users complete github, community work faster.

Target users

  • Developers, testers, and maintainers who handle Other tasks in Focus Code.
  • Teams that already trust workflows or content from ruvnet.
  • Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

  • Read the skill content first to confirm required inputs, expected outputs, and dependencies.
  • Try it on a small task before relying on it for critical work.
  • Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
  • For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

  • Tasks related to github, community that need a reusable execution flow.
  • Converting a community repo, team convention, or personal workflow into day-to-day assistance.
  • Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

  • Results depend on the quality of the original skill content and may need human correction.
  • It does not replace code review, tests, security review, or professional judgment.
  • External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

  • Structured around Other, making it easier to discover and reuse than loose prompt snippets.
  • Marked as GitHub, which helps users judge trust and maintenance expectations.
  • Keeps the original source link available for repository, documentation, or discussion follow-up.
  • Tagged with github, community, so it can be filtered by concrete task intent.

Install and use

Install
Copy Install Command
focus install cost-conversation-cc031c
View source

Detail Preview

SKILL.md

Primary filemarkdown2 KB

name: cost-conversation description: Per-conversation cost view — list every session in cost-tracking with started-at, message count, top model, and total cost argument-hint: "" allowed-tools: Bash

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

Reviews

Overall rating

0.0
0.0

0 comments

No reviews yet