agentleFS
dylanjbarthdylanjbarth/agent-skills/skills/load-balance/SKILL.md

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.

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
  1. Distinctive:

    After the probe, show one row per limit (not one row per agent):

    line 26
  2. Very specific:

    When an agent has error, add one summary row with Auth missing/failed and the error message.

    line 43
  3. Very specific:

    When error is set, include the message and fix hint (codex login, claude /login, sign in to Cursor, or CURSOR_SESSION_TOKEN).

    line 51

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.py

Or 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):

AgentLimitUsed%ResetsNotes

Row rules:

  • Agent — cursor, codex, or claude
  • Limit — label from each limits[] entry (e.g. 5-hour, 7-day Fable, Code review 7-day, Composer / Auto)
  • Used% — used_percent when status: ok; otherwise unknown
  • Resets — human-readable resets_at (or —)
  • Notes — optional tags from JSON: active, severity (e.g. warning), model for 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.