Clade for Codex
This workflow runs directly in Codex. Do not launch the claude CLI or
delegate the workflow to Clade's MCP bridge.
Codex compatibility rules:
- Plugin skills are namespaced. Invoke this workflow explicitly as
$clade:codex-usage; a bare $name does not select the installed Clade plugin.
- Read the nearest
AGENTS.md files for repository instructions. If a project
has only CLAUDE.md, treat it as legacy project guidance and read it too.
- Store new Clade working state under
.clade/ (or ~/.clade/ for personal
state). Existing legacy Claude state may be read for migration, but do not
create new vendor-specific state.
- A
/skill-name reference means the corresponding Codex
$clade:skill-name plugin skill, or the same workflow invoked naturally when
explicit skill invocation is not available.
- Use Codex web, file, shell, image, and subagent capabilities when the source
workflow names a vendor-specific tool. If a capability is unavailable, use
the documented fallback instead of spawning another agent CLI.
- Paths such as
<plugin-root>/... are relative to the installed Clade plugin
containing this SKILL.md; resolve that root before invoking a helper.
Canonical Clade workflow
You are the Codex Usage skill. Show Codex account rate-limit usage or configure
the native Codex status line.
Execute
Resolve this installed skill's directory — the directory containing this
SKILL.md.
Run its bundled helper with Python 3:
python3 <skill-dir>/scripts/codex_usage.py [arguments]
Pass through arguments exactly:
| User request |
Helper arguments |
| no arguments, "usage", "quota" |
none |
| "setup", "add it to my footer" |
setup |
| "minimal footer" |
setup minimal |
| "full footer" |
setup full |
| "style" or "list styles" |
style |
| "minimal/icon/detail style" |
`style minimal |
| "theme" or "list themes" |
theme |
| "theme NAME" |
theme NAME |
| "json" or machine-readable output |
--json |
Report the helper output directly. If setup changed the configuration,
remind the user to start a new Codex session so the footer reloads.
Safety and scope
- Never read, print, copy, or parse
~/.codex/auth.json.
- Do not call private HTTP endpoints directly. The helper uses the authenticated
Codex app-server protocol.
- Plain
setup preserves existing status-line items and only adds the native
five-hour-limit and weekly-limit fields. setup minimal or setup full
may replace only the status_line array because the user explicitly selected
a layout; all other Codex configuration must remain unchanged.
- Do not consume a rate-limit reset credit. This workflow is read-only except
for the explicit
setup, style, or theme commands.
Additional skill reference
Codex Usage
Shows authenticated Codex rate-limit windows and compares usage with a 95%
target pace. It can also add Codex's native five-hour and weekly limit fields to
the TUI footer without replacing existing status-line fields.
Usage
$codex-usage
$codex-usage setup minimal
$codex-usage style icon
$codex-usage theme
$codex-usage theme bird
$codex-usage --json
The helper talks to codex app-server; it does not read or print Codex login
credentials.
Delivery completion
If this workflow changes files or external state:
- Inspect the real final state before responding, including
git status for a
repository task.
- Never report
DONE while task-owned changes are uncommitted. Use or continue
$clade:delivery and create a repository-compliant checkpoint or preserve
the work when committing is unavailable.
- When the user request or trusted repository policy makes publication,
deployment, or live verification part of the task, do not silently downgrade
the result to local-only work.
- If a required delivery transition lacks authority, credentials, a destination,
or reachable external state, report
BLOCKED or NEEDS_CONTEXT rather than
appending a "not committed/pushed/deployed" caveat after DONE.
1---2name: codex-usage-23description: Show Codex rate-limit usage and pace, or configure the native Codex status line4---56# Clade for Codex78This workflow runs **directly in Codex**. Do not launch the `claude` CLI or9delegate the workflow to Clade's MCP bridge.1011Codex compatibility rules:1213- Plugin skills are namespaced. Invoke this workflow explicitly as14 `$clade:codex-usage`; a bare `$name` does not select the installed Clade plugin.15- Read the nearest `AGENTS.md` files for repository instructions. If a project16 has only `CLAUDE.md`, treat it as legacy project guidance and read it too.17- Store new Clade working state under `.clade/` (or `~/.clade/` for personal18 state). Existing legacy Claude state may be read for migration, but do not19 create new vendor-specific state.20- A `/skill-name` reference means the corresponding Codex21 `$clade:skill-name` plugin skill, or the same workflow invoked naturally when22 explicit skill invocation is not available.23- Use Codex web, file, shell, image, and subagent capabilities when the source24 workflow names a vendor-specific tool. If a capability is unavailable, use25 the documented fallback instead of spawning another agent CLI.26- Paths such as `<plugin-root>/...` are relative to the installed Clade plugin27 containing this `SKILL.md`; resolve that root before invoking a helper.2829## Canonical Clade workflow3031You are the Codex Usage skill. Show Codex account rate-limit usage or configure32the native Codex status line.3334## Execute35361. Resolve this installed skill's directory — the directory containing this37 `SKILL.md`.382. Run its bundled helper with Python 3:3940 ```bash41 python3 <skill-dir>/scripts/codex_usage.py [arguments]42 ```43443. Pass through arguments exactly:4546 | User request | Helper arguments |47 |--------------|------------------|48 | no arguments, "usage", "quota" | none |49 | "setup", "add it to my footer" | `setup` |50 | "minimal footer" | `setup minimal` |51 | "full footer" | `setup full` |52 | "style" or "list styles" | `style` |53 | "minimal/icon/detail style" | `style minimal|icon|detail` |54 | "theme" or "list themes" | `theme` |55 | "theme NAME" | `theme NAME` |56 | "json" or machine-readable output | `--json` |57584. Report the helper output directly. If `setup` changed the configuration,59 remind the user to start a new Codex session so the footer reloads.6061## Safety and scope6263- Never read, print, copy, or parse `~/.codex/auth.json`.64- Do not call private HTTP endpoints directly. The helper uses the authenticated65 Codex app-server protocol.66- Plain `setup` preserves existing status-line items and only adds the native67 `five-hour-limit` and `weekly-limit` fields. `setup minimal` or `setup full`68 may replace only the `status_line` array because the user explicitly selected69 a layout; all other Codex configuration must remain unchanged.70- Do not consume a rate-limit reset credit. This workflow is read-only except71 for the explicit `setup`, `style`, or `theme` commands.7273## Additional skill reference7475# Codex Usage7677Shows authenticated Codex rate-limit windows and compares usage with a 95%78target pace. It can also add Codex's native five-hour and weekly limit fields to79the TUI footer without replacing existing status-line fields.8081## Usage8283```text84$codex-usage85$codex-usage setup minimal86$codex-usage style icon87$codex-usage theme88$codex-usage theme bird89$codex-usage --json90```9192The helper talks to `codex app-server`; it does not read or print Codex login93credentials.9495## Delivery completion9697If this workflow changes files or external state:9899- Inspect the real final state before responding, including `git status` for a100 repository task.101- Never report `DONE` while task-owned changes are uncommitted. Use or continue102 `$clade:delivery` and create a repository-compliant checkpoint or preserve103 the work when committing is unavailable.104- When the user request or trusted repository policy makes publication,105 deployment, or live verification part of the task, do not silently downgrade106 the result to local-only work.107- If a required delivery transition lacks authority, credentials, a destination,108 or reachable external state, report `BLOCKED` or `NEEDS_CONTEXT` rather than109 appending a "not committed/pushed/deployed" caveat after `DONE`.
shenxingy