budget-check
/budget-check
A pre-wave usage gate. Launching a multi-agent wave is the most expensive thing an agent does — N concurrent subagents, each burning tokens. /budget-check answers one question before you spend: is the current usage window close enough to its ceiling that starting a wave is reckless? It returns go, no-go, or unknown, and it fails closed — with no usage data it returns unknown, never a convenient "go".
It is deliberately small: a concrete wrapper around the public ccusage reader, not a judgment engine. It does not add a global rule or amend your operating directives — it is a skill you call, so the gate lives at the decision point, not as standing policy.
Structured execution spec:
protocol.yon. Read it for the canonical rules and step sequence; this file is explanation. The two must stay in sync — if you edit one, update the other and refresh the@STAMPdate.
The check — one tool, three verdicts
The skill runs tools/budget-check.mjs, which wraps ccusage blocks --json:
node tools/budget-check.mjs # go/no-go vs 95% of your historical-peak block
node tools/budget-check.mjs --threshold 90 # custom threshold (percent)
node tools/budget-check.mjs --token-limit 200000000 # explicit ceiling instead of the auto peak
node tools/budget-check.mjs --json # machine-readable verdict