usage-limitslisted

Check this Claude plan's live usage limits — the 5-hour and weekly (7-day) rate-limit %s and reset times that actually gate the session, plus context-window fill. Has a `--guard` pacing gate (per-window configurable) for multi-agent fan-outs. Use mid-task to decide whether to keep spawning subagents, before/between waves of a big job, or when the user asks "how close are we to the limit", "how much is left", "when does it reset", or "how full is the context". A compact one-liner (date/time + 5h & weekly %s) is wired as a per-turn hook (`usage --hook`, transcript-suppressed), so every prompt already carries the current time and live usage. Runs the `usage` command (alias `roost-usage`).
moiri-gamboni/roost · ★ 0 · AI & Automation · score 69

Install: claude install-skill moiri-gamboni/roost

# usage-limits — check the 5-hour & weekly limits on demand Run **`usage`** (alias `roost-usage`). Example: ``` ── Claude usage limits ──────────────────────────── 5-hour ███░░░░░░░ 33% resets in 2h40m (pace cap 46%) weekly █░░░░░░░░░ 10% resets in 6d12h (ease cap 26% (sqrt)) context ████████░░ 83% (this session) ────────────────────────────────────────────────── Opus 4.8 · cache 0s old ``` - **5-hour** and **weekly (7-day)** are the caps that throttle the plan. Each shows % consumed and a live "resets in" countdown. Both are **account-global** — shared across every session/agent **and model** on the plan (Fable and Opus draw from the same 5h/weekly pool; the statusline payload has no per-model breakdown, verified: Fable- and Opus-rendered snapshots report identical `resets_at` and %s), so burning either fast in a fan-out blocks everything. - **context** is this session's context-window fill (per-session; decide whether to compact). - No dollar cost — subscription plan, so the API-equivalent $ is misleading. `usage --json` emits raw fields (incl. each window's resolved guard). ## Compact one-liner — `usage --compact` / `usage --hook` (the per-turn hook) `usage --compact` (alias `--oneline`) prints a single token-frugal line: current date/time, then the 5-hour and weekly %s with their **live** reset countdowns (no context/session tokens). It **always exits 0**, so it is safe wherever a non-blocking status line is wanted. ``` Claude usage limits · 2