budget

Probe Anthropic rate-limit headers and render utilization tables.

2|Updated Apr 24, 2026

Search Tags:#anthropic #ndjson #rate limit #headroom #budget probe #oauth refresh #cache fallback

Ready to run

npx skills add https://github.com/geoyws/atmux --skill budget-geoyws

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: budget
Source: https://github.com/geoyws/atmux/tree/main/plugins/atmux/skills/budget
Command: npx skills add https://github.com/geoyws/atmux --skill budget-geoyws

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, curl, flock, date, awk, sed, mktemp, timeout, and includes scripts (resource) components.

What problem does it solve?

It prevents wasted time and failed workflows by determining which configured Claude accounts still have sufficient 5-hour and weekly rate-limit headroom before you start high-cost or parallel work.

Core Features & Use Cases

Cross-account rate-limit probing: Checks live anthropic-ratelimit-unified-* headers for every account discovered under ~/.claude-*/.credentials.json, returning utilization, reset times, and status.
Safe refresh behavior: Automatically warms/refreshes expired OAuth tokens via the claude --print "." trick (unless disabled) to avoid unnecessary 401 failures.
Operational caching and resilience: Writes per-account probe results to ~/.atmux/state/budget-probe-<account>.json, and falls back to cached data on timeouts/network errors while marking entries as stale.
Use case: Before rotating a team’s Claude account or dispatching heavy parallel tasks, verify which accounts are allowed versus rejected and pick headroom-first options to reduce throttling.

Quick Start

Run the budget probe to print a consolidated table of headroom across all your configured Claude accounts.

Frequently Asked Questions about budget

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check Claude API rate limit headroom across multiple accounts before dispatching parallel tasks?▼

Check Claude API rate limit headroom by probing anthropic-ratelimit-unified headers to derive 5-hour and weekly utilization. This cross-account probing returns reset times and allowed or rejected status, enabling headroom-first account rotation to reduce throttling.

What is anthropic rate limit headroom and when do I need to probe it?▼

Anthropic rate limit headroom is the remaining token capacity within 5-hour and weekly windows. Probe it before starting high-cost workflows or parallel agent scheduling to prevent failed requests, wasted time, and operational throttling.

How to monitor cross-account Claude rate limits using curl and jq?▼

Monitor cross-account Claude rate limits by using curl to probe messages endpoint headers and jq to parse the response. The process auto-discovers credentials, probes per-account with timeouts, and writes deterministic NDJSON results.

Does the budget probe work with expired OAuth tokens or network timeouts?▼

The budget probe handles expired OAuth tokens by automatically warming them via a print trick to avoid 401 failures. On network timeouts, it falls back to cached per-account probe results stored locally while marking entries as stale.

Can I use this rate limit probe for parallel agent scheduling and lead dispatch timing?▼

Yes, the rate limit probe targets operational decisions for parallel agent scheduling and lead dispatch timing. It outputs utilization data and allowed or rejected status to help pick accounts with sufficient headroom for token-budget-sensitive workflows.

What dependencies do I need to run cross-account Claude budget probing?▼

Cross-account Claude budget probing requires standard command-line dependencies including curl, jq, flock, date, awk, sed, mktemp, and timeout. These tools enable credential discovery, header parsing, caching, and formatted table rendering.