Borrowing it
Nothing to install: this file belongs to kunchenguid/quota-axi. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kunchenguid/quota-axi/main/AGENTS.mdgit clone --depth 1 https://github.com/kunchenguid/quota-axiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/kunchenguid/quota-axi/agents-md)<a href="https://agentmods.dev/instructions/kunchenguid/quota-axi/agents-md"><img src="https://agentmods.dev/badge/instructions/kunchenguid/quota-axi/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/kunchenguid/quota-axi/agents-md"><img src="https://agentmods.dev/badge/instructions/kunchenguid/quota-axi/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01622 | $0.01622 |
| Opus 5.5 | $0.00649 | $0.00649 |
| Sonnet 5.5 | $0.00324 | $0.00324 |
| Haiku 4.5 | $0.00162 | $0.00162 |
Grade A, and why
quota-axi AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project agent memory
This file is the project's committed home for project-intrinsic agent knowledge: build, test, release, architecture, and sharp-edge notes that should travel with the code.
Provider windows, credentials, cache identity, output tiers, and the TUI are owned by README.md. Follow the section named below instead of restating it here.
- VISION.md is the acceptance policy and sits ahead of what ships. Accuracy of the reported number comes first. README Security Posture is what ships today; do not restate VISION.md wording as a current guarantee.
- quota-axi is data only. It reports the local providers named in the README, including Muse and Higgsfield, and must never route, recommend, rank a winner, order providers preferentially, proxy, intercept, log in, import browser cookies, or mint or rotate a credential. The per-scope
selectionsignal is data for the consumer. The generated skill stays a stub that defers to the CLI (README Agent Skill). - Never exchange a refresh token, and never retain, log, render, cache, or send its value. Delegated refresh checks presence only. Pi brokers may read a stored refresh value only to classify it as a usable literal, then discard it. See README Safety guarantees and README Delegated credential refresh.
- A delegate runs only when the same stored access token is expired, carries a refresh token, and was definitively rejected, and only through
src/providers/delegated-refresh.ts. quota-axi never signals that child. A run that outruns the wait is unmeasured or stale, never a sign-out, and never retires the cache. Leaving a provider read-only is always allowed. - Never read a secret in order to decide cache silence, and never log or render a credential. Cache files are
0600and hold only normalized non-secret snapshots. Do not cache raw provider responses or credential headers (README Cache). - Do not invent a quota figure, window, reset, percentage, or cycle the vendor did not supply. Do not treat an inherited bound as exhaustion without the evidence in README Quota windows. A
shareOfwindow never yields a remaining. Demote fields only in the renderer. - New credential sources follow the checklist in README Provider
state. New remote fetches go throughsrc/lib/http.ts. New process-table reads go throughcurrentUserProcessListArgs. Context-scoped cache identity goes throughCONTEXT_SCOPED_PROVIDERS. - Codex stale cache reuse requires a stored account stamp matching a credential identity the current read actually tried; see README Cache.
- Same-subscription coalescing is shared machinery in
src/providers/accounts.ts: one report per verifiedaccount.accountIdor hashed cachesubscriptionstamp, windows never summed, missing or unverified identity stays separate, and every lane keeps its own cache slot. Codex native/Pi lane folding stays insrc/providers/codex.ts. Claude lanes exist only whenQUOTA_AXI_CLAUDE_PROFILESorQUOTA_AXI_CLAUDE_SWAPopts in; unset, Claude must stay byte-identical to one selected lane. Only the selected profile lane may use the env token or delegated refresh; the claude-swap source runs claude-swap's read-onlycswap list --jsoncommand, which is not a delegated refresh. Contract in README Multiple accounts. --profile-onlyis fail-closed for one Claude or Codex credential file and bypasses other sources, delegated refresh, and the cache (README Profile-only quota reads). Omitting it keeps ordinary discovery.--allow-keychain-promptis the one-time opt-in for a secure-store value read that can prompt. Relay "Always Allow" whenkeychain_access_requiredappears. A missingsqlite3issqlite3_unavailable; do not install system packages.- Provider tests use synthetic stores and mocked Keychain, process, and HTTP boundaries. Never use a live credential, the real
securitybinary, a real refresh, or a provider API. PassrefreshCredentials: falseunless the test is about delegation. - Muse (
muse) is a default unscoped provider and stays read-only. Its only quota read is the Muse CLI's own startup request,POST /muse-code/key, whose response also carries the account's Model API key; parse through a key-allowlist reviver so the key never reaches an object. A live 1.4.0 Power Usage mint body may omitsubs_usage; that is an empty reading, not a missing allowlist key. Do not expand the allowlist without live usage key paths. On macOS the token lives in the login Keychain itemai.meta.dev.credentials/meta, gated by--allow-keychain-promptlike the Cursor CLI source (src/providers/muse-keychain-credential.ts).authpassespresenceOnly: !allowKeychainPromptso a leftover grant marker never fetches the bundle. A skipped present Keychain source is never a sign-out, even when a later sibling is rejected: report the blocked read and preserve the cache. An unreadable or malformed Muse auth file with no working fallback is an operational failure, notauth_required.src/providers/muse-read-gate.tsbounds requests to one per credential perMUSE_KEY_READ_INTERVAL_MSvia a0600ledger of opaque context digests: check andpendingclaim are one locked step, and a request does not leave without that recorded claim. Inside the interval replay and send nothing. A successful empty reading records a non-secret empty-quota marker on that ledger so interval replay returns the same observation; a cache miss after a windowed quota outcome is not turned into an empty reading. Muse is excluded from--max-age/QUOTA_AXI_MAX_AGEfresh reuse, because a macOS Keychain login switch does not change a traced file; the five-minute ledger remains the bound on vendor calls. Muse snapshots are context-scoped (answering source plus a one-way digest of the credential that answered) throughCONTEXT_SCOPED_PROVIDERS. Do not loosen the gate or add a delegate without fresh empirical evidence of the endpoint's rotation behavior. Contract in README Provider notes.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago Changed · +31 tokens per session 94470a13cb7b
- 13d ago Changed · +56 tokens per session 7fbe83d8b4c9
- 20d ago Changed · +4 tokens per session 831b2401c5f4
- 22d ago Changed · +1 lines · +86 tokens per session ca77007913ab
- 29d ago Changed · -86 lines · -10,647 tokens per session 15d1e2dab861
- 1mo ago Changed · +1 lines · +469 tokens per session a08a896d4322
- 1mo ago Changed · +1 lines · +82 tokens per session 68a102e93684
- 1mo ago Changed · +5 lines · +1,049 tokens per session 2938f06470e0
- 1mo ago Changed · +218 tokens per session 5bea59d109e3
- 1mo ago First seen · 122 lines · 10,274 tokens per session scan A c056d56acd6e
quota-axi AGENTS.md is an instructions file published in the GitHub repository kunchenguid/quota-axi (161 stars, last pushed yesterday), licensed MIT. It adds 1,622 tokens to every session, about $0.0065 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.