codex-setup
Skill9 starsChanged 7 days agoMITView on GitHub
Set up, check, restore, diagnose misleading quota colors, or style the cc-hud native footer in Codex CLI when requested. Claude Code uses /cc-hud:setup instead.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- MyMemoAI/openmymemotheir own version, first seen Oct 11, 2026
- sd0xdev/sd0x-dev-flowtheir own version, first seen Oct 8, 2026
- sd0xdev/sd0x-harnesstheir own version, first seen Oct 6, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- MyMemoAI/openmymemo★ 29same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Use the packaged CLI; no global npm installation is needed.
- Very specific: line 26
Use restore-theme codex to restore prior theme preferences when requested.
- Very specific: line 27
Keep theme changes optional.
- Very specific: line 28
Run theme codex again after an upgrade to refresh an unedited installed theme.
- Distinctive: line 42
If setup or restore detects a later user edit, leave that configuration in place and report the conflict.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Use the packaged CLI; no global npm installation is needed. Resolve the plugin root two directories above this SKILL.md, then run:
node "<plugin-root>/dist/cli.js" setup codex
node "<plugin-root>/dist/cli.js" check codexFor a request to check only, run only check. For a request to restore the
previous footer, run restore codex instead of setup. Report the actual result.
Relay the setup/check color note: Codex colors 5h and weekly by the active
syntax theme, independent of remaining quota. For a color complaint, check
the active tui.theme and tui.status_line_use_colors before diagnosing it;
use the color the user reports, never infer the visible color from a percentage.
For a requested visual match or a misleading red/green quota color, run
theme codex. This installs the bundled native CC-HUD theme,
uses a fixed neutral teal accent for limits, and also changes code highlighting.
Tell the user to open /theme, search cc-hud, and press Enter for a
live preview/application. Theme names aren't slash-command arguments.
Use restore-theme codex to restore prior theme preferences when requested.
Keep theme changes optional; ordinary footer setup preserves the user's theme.
Run theme codex again after an upgrade to refresh an unedited installed theme.
Setup requires Node >=18 and Codex CLI >=0.166.0. It edits only
tui.status_line through Codex's configuration API and saves the previous
field in $CODEX_HOME/cc-hud-native.json (default ~/.codex). If Codex is not
on PATH, set CC_HUD_CODEX to its executable or npm bin/codex.js path.
Tell the user to restart Codex to load the saved footer. Display, refresh, theme, quota data, and truncation stay native. Codex percentages for limits are remaining quota. Neither the native nor bundled theme changes color by percentage: 1% left and 93% left share a color. Its appearance approximates the Claude HUD. Plugin updates need no setup rerun unless the release changes the preset.
If setup or restore detects a later user edit, leave that configuration in place and report the conflict. Do not rewrite TOML manually or change other settings, auth, hooks, MCP servers, or the Codex daemon.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

