Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Version 1.0.5 - Fixed token extraction bug in auto-refresh-cron.sh (removed unnecessary quotes handling). - Changed token health check from every 1 hour to every 30 minutes for increased reliability. - Improved OAuth token sync process to be more robust, referencing ~/.claude/.credentials.json. - Updated documentation to reflect changes and add a changelog section.
What This Skill Does
Tracks Claude Code subscription usage across 5-hour session and 7-day weekly quotas. Calculates burn rate to show whether you're under-using, on pace, or at risk of hitting limits before reset. Sends one-time alerts at configurable thresholds and generates daily plain-text reports.
Claude Code's interface doesn't expose burn rate or weekly quota progress, so this fills that gap with plain shell scripts and no external dependencies beyond curl.
When to use it
- Checking session quota remaining before starting a long coding task
- Getting an evening summary of weekly Claude Code consumption
- Deciding whether to use Claude more aggressively or slow down today
- Monitoring burn rate across a Max 100 or Max 200 subscription
- Setting up an automated alert when session usage crosses 50%
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: how much of my Claude Code quota have I used this week?
- 1Runs check-usage.sh, which checks the local 10-minute cache before making an API call
- 2Fetches utilization data from the Anthropic OAuth API if cache is stale
- 3Calculates burn rate by comparing weekly utilization against the expected daily budget for the detected plan
- 4Outputs SESSION and WEEKLY percentages alongside a BURN_RATE status
SESSION=22.0, WEEKLY=49.0, BURN_RATE=OK — user is on pace for their subscription plan
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.