Back to browse
GitHub Repository

Various Claude Skills created along the way

27 starsPython

Claude Skill for temporary cost tracking

by jbdamask·Mar 8, 2026·2 points·0 comments

AI Analysis

●●SolidSolve My ProblemNiche Gem

Real-time cost tracking for Claude Code sessions; saves money intuition before you ship.

Strengths
  • Solves a genuine blind spot—most developers have no idea what iterative API calls cost until production.
  • Clear tabular output with cache hits/writes separated makes hidden cost dynamics visible.
  • Integrates seamlessly into existing Claude Code workflow via Skills API.
Weaknesses
  • Scope limited to Claude; doesn't generalize to other LLM APIs or cross-platform tracking.
  • No historical cost tracking or project-level aggregation—session-only snapshots.
Target Audience

Claude Code users, AI application developers

Post Description

Here's a Claude Skill that lets me turn cost tracking on an off for a particular unit of work.

I use it in interactive Claude Code sessions. For example, if I want to add a Claude API feature to an app, I'll often hack it together first in CC. This skill lets me start and stop tracking so I get get a sense for what the API costs will be.

For example:

> /cost-tracking > [do stuff] > stop tracking

Then I get a nice little table showing tokens and cost for the model that was used:

Haiku cost report (this session's work):

┌───────────────────┬───────────┬─────────┐ │ Category │ Tokens │ Cost │ ├───────────────────┼───────────┼─────────┤ │ Base input │ 182 │ $0.0002 │ ├───────────────────┼───────────┼─────────┤ │ Output │ 3,276 │ $0.0164 │ ├───────────────────┼───────────┼─────────┤ │ Cache writes (1h) │ 25,619 │ $0.0512 │ ├───────────────────┼───────────┼─────────┤ │ Cache reads │ 1,585,531 │ $0.1586 │ ├───────────────────┼───────────┼─────────┤ │ Grand Total │ │ $0.2264 │ └───────────────────┴───────────┴─────────┘

Similar Projects