agentleFS
Sign inStart free
layer5iolayer5io/docs/.agents/skills/quota-axi/SKILL.md

quota-axi

Skill101 starsChanged 4 months agoApache-2.0View on GitHub

Report local Claude, Codex, Cursor, GitHub Copilot, and Grok quota windows via the quota-axi CLI - remaining percentages, reset times, and provider status read from local auth sources, with no routing, recommendation, or provider mutation. Use before deciding whether it is safe to keep spending a provider's quota, when the user asks about usage, rate limits, or remaining quota, or when comparing local provider headroom.

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 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.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use quota-axi whenever you need local quota headroom before deciding whether it is safe to keep working on a provider, when the user asks …

    line 25
  2. Very specific:

    Run npx -y quota-axi for compact TOON output covering supported providers' quota windows.

    line 31
  3. Very specific:

    Run npx -y quota-axi auth to check local auth-source availability without printing secret values.

    line 35
  4. Very specific:

    If quota output reports reason: keychain_access_required, tell your user to run quota-axi --allow-keychain-prompt once and approve Keychain …

    line 38
  5. Very specific:

    After that successful grant, plain quota-axi calls reuse the existing Keychain access marker to refresh live Claude quota without requiring …

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

quota-axi

Report local agent-provider quota windows for routing-aware agents.

You do not need quota-axi installed globally - invoke it with npx -y quota-axi.

quota-axi is data only: it never routes, recommends, proxies, intercepts, logs in, imports browser cookies, or mutates provider state. It reads local provider auth sources and calls first-party provider quota, usage, billing, or entitlement endpoints; it never launches the Claude CLI, so it cannot spend the quota it measures.

When to use

Use quota-axi whenever you need local quota headroom before deciding whether it is safe to keep working on a provider, when the user asks about usage, rate limits, or remaining quota, or when comparing supported local provider headroom side by side.

Workflow

  1. Run npx -y quota-axi for compact TOON output covering supported providers' quota windows.
  2. Scope to one provider with --provider claude or to a subset with --provider cursor,copilot,grok.
  3. Pass --json for the normalized machine-readable model instead of TOON.
  4. Pass --full to include account identity and per-source attempt details.
  5. Run npx -y quota-axi auth to check local auth-source availability without printing secret values.
  6. On macOS, Claude Keychain value reads are skipped by default until the user grants access once. If quota output reports reason: keychain_access_required, tell your user to run quota-axi --allow-keychain-prompt once and approve Keychain access ("Always Allow"). After that successful grant, plain quota-axi calls reuse the existing Keychain access marker to refresh live Claude quota without requiring the flag.
  7. For a managed Codex installation, set QUOTA_AXI_CODEX_BINARY to its absolute executable path. quota-axi uses that exact executable for auth inspection and the read-only app-server fallback, and fails closed if the override is invalid.

Usage

usage: quota-axi [auth] [flags]
commands[2]:
  (none)=quota, auth
flags[6]:
  --provider <claude,codex,cursor,copilot,grok>, --json, --full, --allow-keychain-prompt, --help, -v/--version
examples:
  quota-axi
  quota-axi --provider claude
  quota-axi --provider cursor,copilot,grok
  quota-axi --json
  quota-axi --full
  quota-axi auth

Tips

  • Output is TOON-encoded and token-efficient by default; pass --json only when you need the normalized schema.
  • Exit code 0 means at least one provider returned data (fresh or stale); exit code 1 means every provider failed; exit code 2 means a usage error.
  • Percentages are not comparable across providers - quota-axi never claims one provider's percentage equals another's.
  • Claude --full output exposes the authoritative OAuth profile account.uuid as account.accountId when Anthropic returns one; otherwise the account identity is explicitly marked unverified rather than inferred.
  • The quota cache at ~/.cache/quota-axi/quotas.json only ever holds normalized non-secret snapshots. Fresh provider reports with no windows clear stale provider snapshots instead of caching empty quota. The Claude Keychain access marker lives alongside it and contains no credential values.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.
  • Other versions5 projects use a version of this.

    Word for word · 5

    1. meshery/meshery★ 12k100% same
    2. meshery/meshkit★ 224100% same
    3. layer5io/sistent★ 140100% same
    4. meshery/schemas★ 81100% same
    5. meshery-extensions/kanvas-site★ 42100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use iterate-pr and cut-release.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • SentrySkill

      iterate-pr

      Iterate on a PR until actionable CI passes and high/medium review feedback is addressed. Use for PR CI failures, review feedback, or green-check loops; do not wait for human approval, draft status, or merge gates.

      Also in 4 projects that use this

    • MicrosoftSkill

      cut-release

      Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR (drop internal-only churn, consolidate duplicates), bump pyproject.toml + uv.lock, run the CI-mirror lint chain, and open the release PR. Activate on "ship a release", "cut v0.x", "release prep", "bump and PR", "open release PR", "what kind of release do we need", or any phrasing that ends in opening a release PR -- even when the user does not say "skill". Stops BEFORE tagging; tagging stays a human gate that triggers the release workflow. Refuses to bump to a major (>= 1.0.0) version without explicit operator confirmation.

      Also in 4 projects that use this

  • In this repository7 other files it gives its agents.

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.

Check your setup, free