cost-track
Auto-capture per-session token usage from the Claude Code session jsonl and persist to the cost-tracking namespace
Profile →npx skills add ruvnet/ruflo --skill cost-track --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 Track Reads the active Claude Code session jsonl (`~/.claude/projects/<encoded-cwd>/<session>.jsonl`), tallies assistant-message `usage` per model, computes USD cost using REFERENCE.md pricing, and writes a structured record to the `cost-tracking` AgentDB namespace. This is the **producer** that gives `cost-report` and `cost-optimize` real data to consume. ## When to use - After a meaningful chunk of work, to capture spend for the report. - At session-end to persist the final tally. - Periodically during long sessions (cron-friendly — see `/loop 30m`). ## Steps 1. **Run the tracker** from the project root: ```bash node plugins/ruflo-cost-tracker/scripts/track.mjs ``` The script auto-discovers the session jsonl from the current working directory. To pin a specific session: `TRACK_SESSION=/path/to/session.jsonl`. To dry-run (no memory write): `TRACK_DRY_RUN=1`. 2. **Inspect the markdown summary** — total cost, per-model and per-tier breakdowns, and the persisted memory key. 3. **Verify persistence** — `mcp__plugin_ruflo-core_ruflo__memory_search --query "session-" --namespace cost-tracking` should list the new record. `cost-report` step 1 reads from this namespace. ## Record s
- When to use
- Steps
- Record shape (in cost-tracking namespace)
- Pricing source of truth
- Env overrides
- Cross-references
node plugins/ruflo-cost-tracker/scripts/track.mjs
What does the cost-track skill do?
Auto-capture per-session token usage from the Claude Code session jsonl and persist to the cost-tracking namespace
How do I install it?
Run `npx skills add ruvnet/ruflo --skill cost-track --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.