cost-opt

Files (1)

• SKILL.md

SKILL.md (first lines)

1. First, ensure logs exist by running:
   `python3 ~/.claude/extract_cost.py --append-log --quiet`
2. Read the JSONL cost log files in `~/.claude/cost-log/*.jsonl` and the
   existing `~/.claude/COST-SUMMARY.md`.
3. Recalibrate and update `~/.claude/extract_cost.py` `PRICING` table and the
   `~/.claude/statusline-command.sh` `case "$model_id"` pricing block, based on
   the `~/.claude/cost-log/*.csv` actual extracts from
   - `https://platform.claude.com/cost` (cost-by-day), and
   - `https://platform.claude.com/logs` (historical API logs) –> The user will
     periodically fetch these extracts themselves and upload them to
     `~/.claude/cost-log`.

4. Perform an efficient `/compact` summary on the log files (just changes since
   last summary) and update `SUMMARY.md` with the compacted summary including:
   total spend, spend by model, spend by project, busiest sessions, and trends.
5. Suggest cost optimizations based on the data — e.g., sessions where Opus was
   used for tasks that Sonnet could handle, high cache-creation ratios, or
   sessions with excessive turns.
6. **Ignore and filter out** work done on the `~/.claude` and `~/.awesome`
   directories, in the cost analysis, summary and recommendations.
7. **Formatting rule — escape dollar signs:** In prose sections (bullet points,
   numbered lists, paragraphs), always write `\$` instead of bare `$` to prevent
   Markdown renderers from interpreting `$...$` as LaTeX math. Dollar signs
   inside tables and fenced code blocks do NOT need escaping. Never break a
   dollar amount across lines.

From laurac8r/claude-damn, MIT.

More from laurac8r/claude-damn