usage-limitslisted

# usage-limits Running out of limit halfway through a job is a scheduling failure, not bad luck. The numbers are on disk before the work starts. Read them, size the job against them, and either commit to finishing or cut the job down until it fits. ## 1. Measure ``` node scripts/usage.js ``` Paths here are relative to this skill's own directory, not the project you are working in. Run them from there, or prefix them with the skill's path. This works the same in Claude Code and in Codex. The host is detected from the environment; add `--host codex` or `--host claude` if a machine has both installed and the wrong one is picked. Everything below applies to both unless it says otherwise. It prints the real percentages and reset times from the CLI's own cache, plus a pace measured from the local session transcripts: ``` Window Used Resets in Left Turns left 5-hour 62% 1h 40m $46.0 ~88 weekly 75% 2d 4h $124 ~240 <- binding Recent pace 15 turns in the last hour, $0.164 per turn, effort xhigh ``` `Turns left` is the number that matters. It is the remaining headroom divided by what a turn has actually been costing over the last hour, on this account, at this effort level. Add `--json` when you want the raw fields. If it says no snapshot was found, run `/usage` once in Claude Code and try again. That populates the cache the script reads. In Codex the equivalent is `node scripts/usage.js --r