kunchenguid/quota-axi

cache-architecture

Cache storage locations, permissions, context scoping, isolation rules, and lifecycle management in quota-axi.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/kunchenguid/quota-axi --skill cache-architecture

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

Quota Cache Architecture & Context Scoping

This document details the disk caching architecture, file permissions, context-scoping mechanism, and data retention policies implemented in src/cache.ts.


Cache Storage & Security

  • Path: ~/.cache/quota-axi/quotas.json, or $XDG_CACHE_HOME/quota-axi/quotas.json if XDG_CACHE_HOME is set.
  • File Permissions: Cache files and parent directories must be created with strict 0600 (read/write by owner only) and 0700 permissions.
  • Normalized Data Only: Cache records contain only normalized, non-secret quota snapshot structures.
  • Strict Prohibition: Never persist raw HTTP responses, headers, authorization bearers, refresh tokens, API keys, or browser cookies.

Context-Scoped Providers (CONTEXT_SCOPED_PROVIDERS)

To prevent cross-account or cross-environment cache poisoning, providers whose identity is configuration-dependent or slot-shared are enrolled in CONTEXT_SCOPED_PROVIDERS in src/cache.ts:

  • Enrolled Providers: See CONTEXT_SCOPED_PROVIDERS in `src/cache.ts` for the current set.
  • Context Identifiers: Snapshots carry an opaque SHA-256 context identifier derived from the answering configuration:
  • Claude: Hashed profile and credential-storage selection. claudeCredentialContextId appends an env marker so environment-token readings cannot be served as stale cache for stored-token accounts.
  • Kimi: Home path plus the slot and base URL resolved from config.toml (never the file contents, which contain keys). Prevents mainland China snapshots from serving as global fallbacks.
  • Command Code: Winning source plus the account identity validated by whoami.
  • MiniMax: Answering credential source plus deployment host.
  • ElevenLabs: Credential source plus a one-way SHA-256 digest of the answering API key.
  • Devin: Answering source, the first-party host it was sent to, and a one-way SHA-256 digest of the answering API key; the key never enters the cache.
  • Muse: Answering source plus a one-way SHA-256 digest of the credential that answered (the Muse CLI's stored OAuth access token or an exported META_API_KEY); a since-refreshed token is a cache miss, never a cross-attribution between accounts.
  • Codex: Hashed ChatGPT account ID stored by the specific credential that produced the reading (resolving collisions between lone discovered lanes and Pi entries).
  • Fallback Verification: Stale cache fallback rejects legacy unstamped snapshots or snapshots whose context ID does not match the active configuration.
  • Codex exception: Codex stamps are optional at write time, but stale serving requires ownership. readCachedCodexProvider withholds an unstamped snapshot, and withholds a snapshot whose stored account id is not among the ids the failed reading's tried credentials actually named; a sibling never probed does not vouch for it, and a transient failure is vouched for only by its own credential. A reading whose tried credentials name no account establishes nothing and is withheld from stale fallback. Contract: README Cache.
  • Skip on Unconfirmed: If a reading cannot confirm context identity (e.g. unreadable configuration), quota-axi skips both writing to cache and clearing the cache slot.

Cache Lifecycle & Exclusions

The following fields and statuses are never cached:

  • Non-fresh or empty reads: Only readings with state.status: "fresh", at least one window, and a source other than cache are written (toCacheProvider); every other status and every cache-served report is skipped. failed is an attempt status, not a provider state.status.
  • Stale reads: Stale data is never re-persisted as fresh.
  • Account identities: Explicit account objects are scrubbed before writing.
  • Source attempts: The report's attempts list and attempt diagnostic logs are excluded.
  • Derived pace & runway: pace, runway, and selection signals are dynamic derivations computed from generatedAt vs current time. They must never be frozen into cache.

PHI-safe job counts (jobs.sampled / completed / failed / other) are stored with the snapshot the same way credits is. A snapshot that never carried jobs stays without them; prompts, URLs, ids, and account identity never enter the cache. Higgsfield is excluded from --max-age fresh reuse (excludeFromFreshReuse), matching Muse: a CLI login switch is not a traced file, and the status payload has no stable non-email account discriminator.


Keychain Access Markers

  • Stored alongside the cache directory in ~/.cache/quota-axi/.
  • Must have 0600 permissions.
  • Filename is keyed by a hash of the selected service and account name. Contains no secret material.
  • Permits non-prompting subsequent Keychain value reads once an initial grant is confirmed.
do mesmo repositório

Mais Skills

Todos os Skills