jimmc414

Claude Statusline Plus — Development skill for Claude Code

Development community

Claude Code status line segments: whether your prompt cache is still warm and what a cold start costs, and whether your 5-hour and weekly usage limits will last until they reset at the current pace, w.

How to install Claude Statusline Plus

This entry records only its repository, not the path inside it, so there is no exact command to give. Open jimmc414/claude_statusline_plus and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Claude Statusline Plus does

Claude Code status line segments: whether your prompt cache is still warm and what a cold start costs, and whether your 5-hour and weekly usage limits will last until they reset at the current pace, with the session doing the burning named.

Alternatives in Development

  • Market Segments — Identify 3-5 customer segments with JTBD and product fit 7.8k ★
  • Claude Usage Monitor — Claude Code statusline plugin for 5-hour/7-day quota, context usage, tokens, and reset countdowns in your term 51 ★
  • Brow — Claude Code usage and rate limits in the MacBook notch 50 ★

README

claude_statusline_plus

Claude Code status line segments that show what the CLI knows but does not display: whether your prompt cache is still warm, and whether your usage limits will last until they reset.

![Claude Code status line: cache warm 58m, 5h 85% in yellow with (resets in 16m), 7d 71%, Fable 80%](docs/statusline.png)

cache warm 31m · 5h 12% (resets in 3h00m) · 7d 41% · Fable 50%
cache warm 31m · 5h 53% 3.9× cap 15:36 (resets in 4h20m) · 7d 38% · Fable 50% · top: refactor auth 57%
Segment The question it answers
cache_warm.sh Is the prompt cache still warm, and what will a cold start cost?
usage_forecast.sh At this pace, will my 5-hour, weekly and Fable limits last until they reset, and which session is burning them?
statusline_plus.sh Runs both and joins what they print. The installer uses it when you have no status line of your own.

Each segment is a standalone script with the same contract: status line JSON on stdin, one line on stdout, nothing at all when there is nothing to report, and always exit 0.

Problem

**The prompt cache.** Every request Claude Code sends includes the entire conversation so far. Prompt caching makes that affordable: a cached prefix is read at a fraction of the normal input price. But the cache expires after a period of inactivity, and nothing in the terminal tells you when. So you step away from a 300k-token session, come back 65 minutes later, type "ok, continue", and that one short message re-processes all 300k tokens at full price. On a subscription that is a visible bite out of your usage window. The expiry is invisible, and the cost lands on whichever message happens to come next.

**The usage limits.** A Claude subscription meters usage in a rolling 5-hour window and a weekly one. Claude Code hands the status line both percentages, but a percentage alone does not say whether you will make it. 53% is comfortable three hours into a window and a lockout forty minutes i