DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to check subscription quota before routing a task with Agent Router

Read account usage with the status command so you know which subscriptions still have capacity.

Account pooling. Shared accounts use a reserve floor of 0.40 by default, and the router excludes depleted shared accounts, so check the reserve before routing work that others also depend on.

Who it is forA person sharing a team agent subscription, or running out of quota on a personal plan, who needs to see capacity before starting work.

The problemAgent subscriptions run out or fall into a reserve, and starting a task on a depleted account stalls the work.

The outcomeA list of accounts with current quota, so you can decide whether to route the task or wait.

What you need first

  • Node.js 20 or newer
  • A TypeSafe API key, since routing always calls TypeSafe
  • At least one agent CLI you are logged in to: agent (Cursor), claude (Claude Code), codex, or opencode
  • Herdr, for launching agents without --dry-run
  • A config file with your accounts in the model-router home folder

Steps

  1. Complete the setup steps and add each agent login to the accounts array in .model-router/config.json.
  2. Enable "local-session" in the collectorPreference of each account whose status line cache you want read.
  3. Run router status to confirm the accounts parse.
  4. Run router status --usage to run the full collector chain and show quota.

Prompt for your agent

In the agent-router repo, run `router status --usage` and list each account with its quota and whether it is eligible. Verify that shared accounts show their reserve and that no personal account is excluded only because quota is missing.

Caveat. Quota data for Cursor, Claude Code, and Codex comes only from cache files your own status line scripts write, which the router does not install.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page