Codex reset credit

Skill heyNag/charms/packages/codex-reset-credit/skills/codex-reset-credit

Small, practical powers for coding agents.

Install

npx -y skills add heyNag/charms --skill codex-reset-credit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when the user explicitly asks about Codex reset credits, credit expiry, quota usage, local rate-limit windows, or when Codex limits reset.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.1 KB, as published. Nobody here has run it

codex-reset-credit

Use this skill only when a user explicitly asks about Codex reset credits, available reset credits, reset-credit expiry, Codex quota usage, local rate-limit windows, or when Codex limits reset.

This skill is read-only. It must not redeem credits, consume credits, modify Codex Desktop, edit auth/session files, or change usage-limit state.

Operating Rules

Run the helper script from this skill directory.
Never print access tokens, refresh tokens, account IDs, credit IDs, email addresses, profile image URLs, or raw auth file contents.
Do not show auth file paths. If a local file path is needed for debugging, ask first and prefer redacted paths.
Prefer the direct answer first: available reset credits, next reset-credit expiry, and local rate-limit reset windows.
State the evidence boundary:
- reset credits come from the live Codex/ChatGPT backend endpoint
- rate-limit windows come from local Codex session token_count snapshots
- local snapshots can be stale if Codex has not emitted recent token-count events
If auth/session state is missing or the endpoint fails, report the plain safe error and any local-only rate-limit data that was still available.

Invocation

From this skill directory:

python3 scripts/check_reset_credits.py

Useful options:

python3 scripts/check_reset_credits.py --json
python3 scripts/check_reset_credits.py --no-live
python3 scripts/check_reset_credits.py --thread-id <thread-id>
python3 scripts/check_reset_credits.py --session-file <absolute-path-to-rollout.jsonl>
python3 scripts/check_reset_credits.py --timezone America/Los_Angeles

Use --no-live when the user only wants local rate-limit reset windows or when network/backend access is not appropriate. Use --json when another tool or agent needs structured sanitized output.

Response Shape

Unless the user asks for raw JSON, return:

Reset credits available
Next credit expiry, if known
Primary rate-limit reset window
Secondary rate-limit reset window, if present
Evidence boundary and any staleness warning
Safe error details, if any

Keep the answer short. Do not paste full JSON unless requested.

Failure Handling

Missing Codex auth: say local Codex auth was not found or not usable.
Endpoint error: say the live reset-credit endpoint failed and include the safe HTTP/network category.
Missing session snapshots: say no local Codex rate-limit snapshots were found.
In all cases, do not reveal tokens, account IDs, auth file contents, or raw local auth paths.

Source Note

Keep edits in this repo under packages/codex-reset-credit, then run make build-packages and make public-check.