codex-usage-status
Codex usage status (quota + pace)
Quick start
Run the bundled CLI script (it reads credentials implicitly via openclaw status --usage --json, so no API keys are needed):
python3 scripts/codex_usage_status.py
# or
./scripts/codex_usage_status.py
Common options:
./scripts/codex_usage_status.py --provider openai-codex
./scripts/codex_usage_status.py --json
What the script reports
- Provider plan name (when available)
- Usage windows (example labels:
5h,Day,Week) with:- Used %
- Reset time (UTC) + time remaining
- Pace projection
Pace definition
Pace is a simple end-of-week projection computed from the provider’s Day window usage percent.
The week window is anchored to the Day window reset time:
week_end = Day.resetAtweek_start = week_end - 7 days
Formula:
- Basis:
Day.usedPercent(different label, same signal) - Usage rate:
current_used_percent ÷ time_elapsed_since_week_start - Projection:
current% + (rate × time_remaining_in_week)
If Day.usedPercent is missing or 0%, Pace is 0%.
More from luongnv89/skills
ollama-optimizer
Optimize Ollama configuration for the current machine's hardware. Use when asked to speed up Ollama, tune local LLM performance, or pick models that fit available GPU/RAM.
126logo-designer
Generate professional SVG logos from project context, producing 7 brand variants (mark, full, wordmark, icon, favicon, white, black) plus a showcase HTML page. Skip for raster-only logos, product illustrations, or full brand-guideline docs.
122code-optimizer
Analyze code for performance bottlenecks, memory leaks, and algorithmic inefficiencies. Use when asked to optimize, find bottlenecks, or improve efficiency. Don't use for bug-hunting code review, security audits, or refactoring without a perf goal.
76code-review
Review code changes for bugs, security vulnerabilities, and code quality issues — producing prioritized findings with specific fix suggestions. Don't use for performance tuning, writing new features from scratch, or generating test cases.
75idea-validator
Evaluate app ideas and startup concepts across market viability, technical feasibility, and competitive landscape. Use when asked to validate, review, or score a product idea. Don't use for writing a PRD, detailed go-to-market plans, or financial/investor pitch decks.
70test-coverage
Generate unit tests for untested branches and edge cases. Use when coverage is low, CI flags gaps, or a release needs hardening. Not for integration/E2E suites, framework migrations, or fixing production bugs.
63