load-balance
Skill1 starsChanged 4 months agoMITView on GitHub
Report coding-agent plan usage headroom across Cursor CLI, Codex, and Claude Code, rank by lowest used percent, and recommend a default. Use when choosing where to run work, checking quota before delegating, comparing agent capacity, or when the user mentions load balance, usage limits, or which agent has headroom.
In this repository2 other files it gives its agents.
- agent-delegateSkill
- babysitSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
After the probe, show one row per limit (not one row per agent):
- Very specific: line 43
When an agent has error, add one summary row with Auth missing/failed and the error message.
- Very specific: line 51
When error is set, include the message and fix hint (codex login, claude /login, sign in to Cursor, or CURSOR_SESSION_TOKEN).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Load balance
Report plan usage headroom across Cursor, Codex, and Claude Code. Read-only — no account switching, no spawning agents.
Run the probe
From this skill directory:
python3 scripts/usage.pyOr pass an absolute path to scripts/usage.py when the skill is installed elsewhere.
The script prints normalized JSON to stdout. Parse limits on each agent before rendering.
Render the table
After the probe, show one row per limit (not one row per agent):
| Agent | Limit | Used% | Resets | Notes |
Row rules:
- Agent —
cursor,codex, orclaude - Limit —
labelfrom eachlimits[]entry (e.g.5-hour,7-day Fable,Code review 7-day,Composer / Auto) - Used% —
used_percentwhenstatus: ok; otherwiseunknown - Resets — human-readable
resets_at(or—) - Notes — optional tags from JSON:
active,severity(e.g. warning),modelfor scoped Claude limits
Sort agent groups by ranking score (lowest minimum used_percent across that agent's limits first). Within an agent, keep limits in the order returned by JSON.
Mark the recommended agent on its tightest limit row (lowest used_percent for that agent) with recommended in Notes. If recommended is null globally, say no recommendation.
When an agent has error, add one summary row with Auth missing/failed and the error message.
Stop here
This skill does not spawn or resume agents. For cross-agent CLI delegation and session monitoring, use $agent-delegate and $babysit.
Errors
When error is set, include the message and fix hint (codex login, claude /login, sign in to Cursor, or CURSOR_SESSION_TOKEN).
Probes use undocumented vendor endpoints and may break. See references/output-contract.md.
Example
Use $load-balance before I pick where to run this refactor.Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

