ruflo-token-audit

# Claude Code Usage Audit (ruflo-token-audit) A **comprehensive** picture of Claude Code usage, built from the local session transcripts in `~/.claude/projects/**/*.jsonl` (each assistant message records its token usage, tool calls, model, and metadata). This is **not limited to "tokens ruflo burns"** — it summarizes the activity visible in retained Claude Code transcripts (including recorded subagent and tool activity) and answers two questions: *where is my usage going?* and *is any of it runaway automation?* This skill is **self-contained** — it bundles its own engine, so it works even if the full agentic-kit kit isn't installed. ## When to use Trigger on: "where are my tokens/usage going", "why is my usage so high", "break down my Claude Code activity", "I'm hitting my Max/Pro limit", "what am I spending tokens on", "is the plan worth it". Also proactively if the user mentions surprising usage. ## Procedure 1. **Run the bundled engine.** Prefer the copy that ships *inside this skill* (works with no kit install); fall back to the PATH command if present: ```bash # self-contained (always available wherever this skill is installed): python3 ~/.claude/skills/ruflo-token-audit/scripts/ruflo-token-audit.py --days 7 # …or, if the agentic-kit kit put it on PATH: ruflo-token-audit --days 7 ``` - Honor any window the user gives ("past month" → `--days 30`). - `--top N` widens each section; `--json` gives machine-readable output; `--no-daemons` ...