Codex Usage Limits Monitor
Monitors Codex quota consumption, predicts limit exhaustion times, and analyzes token usage patterns directly from local logs using Sipcode.
The Codex Usage Limits Monitor skill leverages the Sipcode CLI to analyze local Codex logs and provide clear visibility into your 5-hour, weekly, and 30-day token limits. It helps developers track exactly how much quota remains, when reset windows will occur, which projects or automated reviews consumed tokens, and whether a limit has potentially decreased over time. By calculating real-time burn rates and run-out estimates in your local timezone without reading or exposing raw log files, this skill ensures you never hit unexpected rate limits during critical development workflows.
Key Features
01Presents unrounded local timezone timestamps without exposing raw log data
02Tracks 5-hour, weekly, and 30-day Codex quota consumption in real time
03Detects historical limit changes and potential quota cuts over time
04Identifies top token-consuming sessions, directories, and auto-reviews
05Calculates token burn rates and projects estimated limit run-out times
0646 GitHub stars
Use Cases
01Checking remaining Codex usage and exact reset times before starting large refactors
02Investigating unexpected quota drops to identify token-heavy coding sessions
03Verifying historical tokens-per-percent ratios to see if plan quotas were modified