codex-usage-status

Retrieve Codex usage, quota windows, and pace projections from JSON output.

104|15|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/luongnv89/skills --skill codex-usage-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-usage-status
Source: https://github.com/luongnv89/skills/tree/main/skills/codex-usage-status
Command: npx skills add https://github.com/luongnv89/skills --skill codex-usage-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates the retrieval and presentation of Codex usage, quota windows, and pace projections.

Core Features & Use Cases

  • Real-time usage views: display current usage windows (Day, Week, etc.) with reset times and remaining time.
  • Pace projections: compute end-of-week usage pace anchored to the Day window reset, helpful for capacity planning.
  • Flexible output: supports human-friendly prints and machine-readable JSON for integrations.

Quick Start

Run the codex_usage_status.py script to view your Codex usage and projected pace.

Frequently Asked Questions about codex-usage-status

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

FAQPage Schema
How do I monitor OpenAI Codex usage and quota limits from the command line?

You can monitor OpenAI Codex usage by running the codex_usage_status script, which reads usage data via openclaw status and displays current quota windows alongside remaining time.

Can I forecast remaining Codex quota across a workweek for capacity planning?

Yes, you can forecast remaining Codex quota by computing end-of-week usage pace anchored to the Day window resetAt, which helps project whether your current rate will exceed the weekly limit.

How do I get machine-readable JSON output for Codex usage data?

To get machine-readable JSON output for Codex usage data, run the script with JSON formatting options to parse provider windows and output structured data suitable for integrations.

What is the best way to track day and week quota reset times for Codex?

The best way to track quota reset times is to automate retrieval of usage windows, which presents the Day and Week resetAt timestamps so you know exactly when limits refresh.

Do I need openclaw installed to check Codex usage pace and quota windows?

Yes, you need openclaw installed because the script reads usage data directly from the openclaw status --usage --json command to parse provider windows and compute pace projections.

Why does my Codex usage pace projection reset at unexpected times during the week?

Codex usage pace projections reset based on the Day window resetAt timestamp, meaning the pace calculation anchors to daily resets rather than continuous weekly averages.