Skip to main content

cost-conversation

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

설치로 이동

소스 정보

저장소
ruvnet/ruflo
최근 소스 활동
2026년 5월 5일 04:04
감지된 SKILL.md 언어
영어
스타
73,010
포크
8,665

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
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: ```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 / 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
GitHub에서 보기