cx-balance

A command that shows how much Codex usage remains in the current five-hour and seven-day limits, plus reset times.

In plain words
What is it for?
Use it to check remaining capacity before running delegated Codex work; the figures may only reflect the last interactive Codex turn.
Why use it?
It helps explain whether a task may be limited by Codex rate limits, while showing the latest available snapshot.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/rbinar/cli-dispatch/cx-balance
Clone the repo
git clone --depth 1 https://github.com/rbinar/cli-dispatch
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 169 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.00169
Opus 5 $0.00010 $0.00084
Sonnet 5 $0.00004 $0.00034
Haiku 4.5 $0.00002 $0.00017

Measured yesterday against content hash 70e814fb378f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cx-balance scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/cli-dispatch/commands/cx-balance.md · 16 lines

What it actually says

!bash "${CLAUDE_PLUGIN_ROOT}/scripts/cli-dispatch-balance.sh" --backend codex

The Codex usage report above already ran — do NOT run it again. Summarize the 5h and 7d windows as % left plus reset time.

The CLI persists rate-limit payloads in on-disk session records; these are the same numbers as /status inside the codex TUI. The snapshot is only as fresh as the last interactive codex turn, because exec/-q runs report rate_limits:null. There is no native scriptable DeepSeek equivalent here. Never print a key VALUE.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 16 lines · 20 tokens per session scan A 70e814fb378f

Subscribe to this mod's changes

cx-balance is a command published in the GitHub repository rbinar/cli-dispatch (5 stars, last pushed 13d ago), licensed MIT. It adds 20 tokens to every session and 169 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.