codex-ratelimit-notify

name	codex-ratelimit-notify
description	Send an IFTTT mobile push "codex rate limit detected" when an OpenAI Codex CLI run hits a rate/usage limit. The companion codex skills (/codex-review, /codex-2nd, /codex-research, /codex-writer, /codex-translator) fire this automatically via codex-rate-limit.js. Invoke manually whenever a codex run that BYPASSES that path — /codex-imagegen, /codex:codex-rescue, or an ad-hoc `codex exec` — shows "you've hit your limit", "rate limit", "usage limit", "too many requests", "quota exceeded", "429", or a reset time, even if the flow otherwise stays silent. Also use to test the notification.
allowed-tools	["Bash(node *)"]

Codex Rate Limit → IFTTT Notify

Fire a mobile push "codex rate limit detected" the moment an OpenAI Codex CLI run hits a rate/usage limit. This matters because the codex skills deliberately silently fall back to Opus and never surface the limit in the terminal — so a phone push is the only way the user learns Codex is throttled.

How it's wired (usually automatic)

All rate-limit state, notification, and dedupe live in one script: $HOME/.claude/scripts/codex-rate-limit.js.

The five companion codex skills (/codex-review, /codex-2nd, /codex-research, /codex-writer, /codex-translator) already run codex-rate-limit.js check-output after each Codex run. When it detects a limit it marks a lockout and fires the push — so for those skills the notification happens on its own. You do not need this skill for them.

When to invoke manually

Some Codex paths bypass codex-rate-limit.js entirely: , , and any ad-hoc you run directly. If Codex output on one of those paths shows a rate/usage limit, funnel it into the same script so both the push and the shared lockout happen: