Victor Statusline — Git skill for Claude Code

victor-statusline

Rich, information-dense status lines for **Claude Code** and **GitHub Copilot CLI** — the one-line bar at the bottom of the terminal that tells you what the agent is costing you, how much quota is left, and whether you are about to throw money away.

Both are plain shell scripts with no dependencies beyond `jq`, `awk`, `bc` and `python3`. Take them as they are, or read the docs and build your own — each doc explains not just *what* every glyph means but *why* it was designed that way, which is the part worth stealing.

Opus 4.8/xhigh 50K/1M | ↗98% left / 4:47 | ✻0.5 ⊂ $25 | +24% = 70% / 1d1h
🤖 opus-4.8 · high · 55K/1M | 6759 AIC (96%)↗ left | resets in 7d 4h

What the bar actually says

Five annotated shots, one per situation. Every figure in them is synthetic — they are rendered from the real scripts fed hand-written payloads, so nothing here is anyone's actual quota or spend (`docs/screenshots/`).

**Claude Code on a Pro/Max subscription** — the full five segments:


**The part that pays for itself** — the prompt-cache clock. Cached input bills at 0.1×, rebuilding a prefix at 1.25× (5-minute cache) or 2.0× (1-hour), so walking away for an hour with 300 K of Opus context loaded costs about three dollars the moment you type again — and nothing on screen would otherwise say so, because the turn just looks expensive. Four moments of one session: warm, about to expire (the loss **priced before it happens**), expired, and the post-mortem on a turn that already paid it:


**A fan-out in flight** — the one chip that is not always there. Claude Code's own agent list never says *which model* each subagent got, and that is what decides whether a 24-way fan-out costs cents or tens of dollars:

![The subagent chip, annotated](docs/screensh