codex-context-budget-audit

Analyze Codex startup context budgets and report phase-separated token estimates.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/pingqLIN/UniText --skill codex-context-budget-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-context-budget-audit
Source: https://github.com/pingqLIN/UniText/tree/main/runtime/skills/codex-context-budget-audit
Command: npx skills add https://github.com/pingqLIN/UniText --skill codex-context-budget-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Codex startup and initial-context budgets are often opaque; this skill audits local sources to reveal token overhead and surface usage across configurations, plugins, and memories.

Core Features & Use Cases

  • Phase-separated CLI auditing: reports memory, AGENTS/workspace instructions, skill and plugin manifests, and MCP surfaces with token estimates.
  • Local visualization: provides ASCII charts and a Codex-ready Markdown dashboard for quick inspection.
  • Baseline comparisons: supports saving and comparing baseline runs to track changes over time.

Quick Start

Run the CLI against a chosen workdir or Codex home to generate a local context-budget report.

Frequently Asked Questions about codex-context-budget-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my Codex context budget and token usage?

To audit your Codex context budget, run the CLI against your workdir or Codex home directory. It reports phase-separated token estimates for memories, AGENTS instructions, and skill manifests, outputting ASCII charts and optional Markdown dashboards.

How are token estimates calculated for Codex startup costs?

Token estimates for Codex startup costs are computed from character counts using deterministic rules. The audit analyzes locally observable sources including memories, workspace instructions, and plugin skill manifests to reveal token overhead.

Do I need a specific directory structure to audit context token overhead?

Yes, auditing context token overhead requires the presence of the Codex home directory and a valid config.toml file. The CLI scans this local environment to surface token usage across configurations, plugins, and memories.

Can I compare context token usage across different Codex configurations over time?

Yes, you can compare context token usage over time by saving and comparing baseline runs. The audit tool supports tracking changes in your Codex startup context budget by evaluating phase-separated token estimates against previous baselines.

What is the best way to visualize Codex startup costs locally?

The best way to visualize Codex startup costs locally is by generating an ASCII chart or Markdown dashboard. The CLI provides phase-separated reports of memory and skill manifest token estimates for quick visual inspection of your context budget.

Why does my Codex startup context budget seem unnecessarily large?

Your Codex startup context budget may seem large due to opaque token overhead in local sources. Auditing memories, AGENTS instructions, and plugin manifests reveals phase-separated token estimates to help you identify and reduce unnecessary usage.