What problem does it solve? Long implementation plans executed by Claude Code can exhaust a subscription's 5-hour or weekly rate-limit window mid-step, leaving work half-finished. This Skill measures quota consumption from local transcripts so execution stops cleanly at a step boundary instead of part-way through a step. ## Core Features & Use Cases - Quota Calibration: Converts a /usage percentage or past rate-limit rejections into a stored per-subscription capacity, persisted in ~/.claude/usage-budget.json. - Per-Step Measurement: Runs claude-budget.js raw --since <timestamp> at each step boundary to record what each step cost, then estimates the next step from the worst observed cost with a 1.5x margin. - Stop Rule and Notification: Halts before a step the remaining budget cannot cover, reports consumption figures, and sends a push notification so an absent user knows why execution stopped. - Use Case: On a standard Team seat, a 9-step migration plan is executed step by step; after step 5 the remaining 3.9M units cannot cover the estimated 4.7M needed, so the agent stops, reports the figures and the window reset time, and leaves task.md ready to resume. ## Quick Start Ask the agent to budget this plan against my Claude subscription quota and stop at a step boundary before the 5-hour window runs out.
