Menú
Per-conversation cost view — list every session in cost-tracking with started-at, message count, top model, and total cost
Spawn nested sub-agents (agents that spawn sub-agents, up to depth=5) via Claude Code's native Task tool — for context-managed deep delegation
Author a workflow — either an MCP workflow template (persisted, lifecycle) or a native .claude/workflows/*.js orchestration script (agent/parallel/pipeline fan-out)
Run a workflow — drive an MCP workflow lifecycle (execute/pause/resume/cancel) or invoke + resume a native .claude/workflows/*.js orchestration via the Workflow tool
Side-by-side comparison of ruflo vs HAL vs other GAIA harnesses — capability gaps, design decisions, and improvement roadmap
Diagnose why a GAIA question failed — extract trace, classify failure mode, and propose a fix
Walk through a complete GAIA benchmark→submit flow — from key resolution through HAL-compatible package generation
| 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-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.
CONV_NAMESPACE=cost-tracking-<project>.Run the script from anywhere:
node plugins/ruflo-cost-tracker/scripts/conversation.mjs
Optional env:
CONV_FORMAT=json — emit JSON instead of markdownCONV_LIMIT=20 — show only the most recent N conversationsCONV_NAMESPACE=cost-tracking — override target namespaceInspect 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).
cost-track — the producer that populates cost-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