Agent skill · data analytics · affaan-m
context-budget
Routes live context checks to the native Codex or Claude Code meter without scanning files, and performs a bounded static component audit only when explicitly requested. Use for context-budget requests about remaining capacity or installed context overhead.
Why this skill is useful
Provides domain-specific knowledge on token consumption patterns and actionable optimizations that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
Context Budget Use the provider's native meter for live session usage. Keep the separate, estimated installation audit behind an explicit opt-in. Default: Live Context Treat an invocation with no audit request as a live-context request. This includes requests for the current window, remaining capacity, headroom, token usage, or a context breakdown. For this default path: Do not call or use tools. Do not scan or read files. Do not run shell commands, provider CLIs, debug logging, or MCP discovery. Reply with only the native command and one short explanation. Route by the active harness: Harness Native command Guidance --- --- --- Codex CLI /status Shows current token usage and remaining context capacity. Use /statusline and enable Context stats plus Token counters for a persistent footer meter. Codex app /status Shows current thread context usage and rate limits. Claude Code /context Shows the live context breakdown. Use /context all for expanded items. Other or unknown None verified State that ECC cannot read live provider state and ask which harness is active. These commands are documented in the Codex command reference and Claude Code command reference. A skill cannot invoke a TUI slash command on the user's behalf. Never replace the native command with an estimated scan and never infer an audit request from phrases such as “context is heavy” or “how much is left.” Explicit Static Audit Run an installation/configuration audit only when the user explicitly says --audit, “audit installed components,” or equivalent unambiguous wording. --verbose changes report detail; it does not opt into an audit by itself. If the audit scope is ambiguous, ask for the harness and installation root before reading anything. Keep every audit bounded and read-only: 1. Inspect only the named plugin/install root and the named harness's known configuration files. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/context-budget--2e3420