Skip to content
Back to skills

Limit

ASecurity

Show Claude and Codex subscription usage windows in one colored screen, live where possible. Use when the user asks "limit", "quota", "how much usage is left", or before choosing which model/pool to delegate a task to.

  • 64 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 24, 2026
ai-agentspythonrustswiftbashapi

Works with

  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 24, 2026

npx -y skills add avenoxai/avenoxskills --skill limit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Limit?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Limit
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/avenoxai-limit/badge)](https://www.skillsdirectory.com/skills/avenoxai-limit)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: limit
description: Show Claude and Codex subscription usage windows in one colored screen, live where possible. Use when the user asks "limit", "quota", "how much usage is left", or before choosing which model/pool to delegate a task to.
---

# Limit

Run the script that ships next to this file (`python` instead of `python3` on Windows;
adjust the path if you installed the skill somewhere else):

```bash
python3 ~/.claude/skills/limit/scripts/limit.py --color always
```

Show the output verbatim before summarising it — do not paraphrase the numbers.

A window whose warnings include `stale`, `window expired`, or `live fetch failed`
is **unknown, not empty**. Don't treat its percentage as current.

## Acting on it

Each window has its own wall, and the reset time matters as much as the percentage:

| Reading | Do |
|---|---|
| Both windows of a pool clear | Use the pool normally. Don't hedge or narrate the number. |
| A window within ~5 points of full | Narrow the work: fewer parallel jobs, cheapest model that can carry it, sequential. Say the number once. |
| 5-hour window at the wall **and resets within ~30 min** | Wait for the reset. Don't hand off to the other pool or start a long run that will be cut in half. |
| Weekly window at the wall | It won't come back for days: hand the work to the other pool if *both* of its windows are clear, otherwise keep it in the main loop or queue it. |
| Both pools at a wall, or a window unknown | Delegate nothing. Report both numbers and ask. |

The fullest *valid* window in each pool is binding — a 12% 5-hour window next to
an exhausted weekly window means the pool is exhausted. Keep a few percent in
reserve for whatever must run at the end of a session (handoff notes, summaries):
a job that dies mid-flight costs more than one that never started.

## Sources, in order

- **Claude**: live `https://api.anthropic.com/api/oauth/usage` call using the token
  in `~/.claude/.credentials.json` → optional `--claude-observation PATH` file →
  `~/.claude.json` cache (`cachedUsageUtilization`, only refreshed by an interactive
  `/usage` call, can be hours stale).
- **Codex**: CodexBar's local cache: `%APPDATA%/CodexBar/codex-accounts/snapshots.json`
  on Windows, `~/Library/Application Support/CodexBar/codex-account-snapshots.json`
  on macOS (Swift Codable format), or `$XDG_CONFIG_HOME/CodexBar/codex-accounts/snapshots.json`
  on Linux (`~/.config` by default, when a compatible writer exists). Then the
  newest dated core `rate_limits` event in up to 40 recent files under
  `$CODEX_HOME/sessions/**/*.jsonl` (`~/.codex` by default). File modification
  time never stands in for measurement time. A malformed trailing line does
  not erase the last valid event. A newer empty measurement remains unknown.

CodexBar cache files are not live fetches. Older than 45 minutes, future-dated,
undated, or expired measurements are unknown. `limitReached` sentinels contain
no trustworthy per-window percentages and are shown as unknown. Multiple
accounts require `--codex-account ID` using the ID from the local snapshot file;
records from different accounts are never combined. An unavailable selected
account does not fall through to unscoped session data. Session fallback cannot
prove that an event belongs to the currently signed-in account.

The Claude live path supports the credentials JSON file, not macOS Keychain-only
credentials. In that case it falls back to observations/cache with a warning.
The dashboard does not log tokens or follow authenticated HTTP redirects.

## `--claude-observation` file schema

Wire your own statusline/hook to write a small JSON snapshot more often than the
`/usage` cache refreshes, then pass its path with `--claude-observation`:

```json
{"epoch": 1758100000, "five": 18.0, "seven": 92.0, "five_reset": 1758113500, "seven_reset": 1758350000}
```

`epoch` (unix seconds), `five`/`seven` (0–100, the 5-hour/7-day window percentages)
are required; `five_reset`/`seven_reset` (unix seconds) are optional. Older than 45
minutes is ignored. All-zero values are treated as **unreadable**, not an empty pool
— an upstream HTTP 429 can write `0` where it means "could not measure".

## Limits

- No per-model weekly windows for Claude (e.g. a Max-plan Opus-specific window) —
  whatever extra windows the live endpoint returns are shown, but nothing is
  synthesized if it doesn't return them.
- CodexBar is optional; without it the script falls back to session rollout files,
  which are only written while `codex` is running and can be stale for days.
- These are subscription usage windows (percent of a rolling quota), not token counts.

Files in this skill

  • SKILL.md4.6 KB
  • scripts/limit.py24.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.