Codex Quota

ReviewAudited by ClawScan on May 10, 2026.

Overview

The skill mostly matches its quota-checking purpose, but its all-accounts mode rewrites your local Codex authentication file and may not restore it if something goes wrong.

This skill appears to be a legitimate quota checker, but be careful with `codex-quota --all --yes`: it rewrites `~/.codex/auth.json` to switch accounts. Before using that mode, make sure you trust the saved account files and consider backing up your Codex auth file.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Medium

#ASI03: Identity and Privilege Abuse

What this means

Using all-account mode can change which Codex account is active locally and relies on saved Codex account files.

Why it was flagged

The skill uses local Codex session and authentication/profile files. This is disclosed and purpose-aligned for quota checking, but it crosses an account/credential boundary that users should understand before using multi-account mode.

Skill content

The skill reads from:
- `~/.codex/sessions/`
- `~/.codex/auth.json` ...
⚠️ With `--all --yes`, the skill temporarily overwrites `~/.codex/auth.json` to switch between accounts

Recommendation

Use --all --yes only when you intentionally want the tool to access saved Codex accounts, and consider backing up ~/.codex/auth.json first.

Medium

#ASI08: Cascading Failures

What this means

A failed or interrupted run could leave Codex logged in as a different account, or could leave the auth file missing or altered.

Why it was flagged

The script restores the authentication file only after processing accounts and silently ignores restoration errors. If the process is interrupted or restoration fails, the user's persistent Codex auth state may remain changed.

Skill content

# Restore original auth.json exactly (best-effort)
try:
    ...
    auth_file.write_bytes(original_auth_bytes)
except Exception:
    pass

Recommendation

The skill should restore auth.json in a finally block, keep a durable backup, report restore failures, and ideally avoid direct credential-file replacement if a safer Codex account-selection mechanism exists.

Low

#ASI05: Unexpected Code Execution

What this means

Running --fresh or --all may contact Codex, create session log entries, and consume a small amount of quota.

Why it was flagged

The --fresh and --all workflows run the local Codex CLI. The command is hardcoded and purpose-aligned, but it creates a live Codex interaction rather than only reading cached logs.

Skill content

subprocess.run(
    ["codex", "exec", "--skip-git-repo-check", "reply OK"],
    cwd=Path.home(),
    capture_output=True,
    timeout=60
)

Recommendation

Use the default cached mode when you do not need a live quota refresh; use --fresh or --all only when a live Codex call is acceptable.