Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/viisopen/get-codex-theme/manage-codex-themenpx skills add ViisOpen/get-codex-theme --skill manage-codex-themegit clone --depth 1 https://github.com/ViisOpen/get-codex-themeWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00092 | $0.00851 |
| Opus 5 | $0.00046 | $0.00426 |
| Sonnet 5 | $0.00018 | $0.00170 |
| Haiku 4.5 | $0.00009 | $0.00085 |
Grade A, and why
manage-codex-theme scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Codex Themes
Use the pinned public CLI so the commands match this Plugin release:
npx -y [email protected] --help
Safe workflow
- Run
npx -y [email protected] status --jsonandnpx -y [email protected] doctor --jsonbefore changing runtime state.doctoris offline unless--liveis explicitly supplied. - Install and select a published theme with
npx -y [email protected] use THEME@VERSION, or an exact local release candidate withnpx -y [email protected] use PACK_DIRECTORY. This does not launch, close, or restart Codex. For local QA, verify thatstatus --jsonreports the same id and version as the source manifest. - If the compatibility runtime is already active, switch with
npx -y [email protected] switch THEME; the runtime applies the new pointer without moving native Codex controls. - Ask for explicit confirmation before running
launch,resume,--launch, or--restart. State that these use an unofficial loopback-only CDP layer. Never infer restart permission from a request to install or switch a theme. - Verify with
npx -y [email protected] verify. Add--screenshot ABSOLUTE_PATH.pngonly when the user asked for a capture and the destination is known. - Use
pausefor a temporary stock appearance while retaining the selected theme. Userestoreto restore the previous pointer (or remove the active pointer when none exists), then tell the user to reopen Codex normally for the definitive stock appearance. Use the platform restore command when a live compatibility session also needs to be stopped. Useuninstall THEMEonly after confirming it is not active; reserve--forcefor an explicit user request. - For pre-publish QA, require a clean demo workspace and inspect welcome branding, Home, a normal Task, sidebar menus, expanded terminal, Settings, banners and Dismiss actions, dialogs and Review actions, inputs, selected/disabled states, and a narrow window. Ask the user for visual confirmation; command success alone is not approval.
- Test restore before declaring local QA complete. If the user wants to keep testing, reselect the exact local pack only after restore succeeds.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 62 lines · 92 tokens per session scan A b47d6a285a58
manage-codex-theme is a skill published in the GitHub repository ViisOpen/get-codex-theme (1 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 851 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
codedrobe-theme
Create, inspect, convert, apply, replace, verify, troubleshoot, update, publish, or restore reversible CodeDrobe themes for supported Chromium/Electron AI desktop apps, including OpenAI Codex, Tencent WorkBuddy, QoderWork (CN/global), and TRAE SOLO (global/CN). Use when a user asks to turn an attached or local…
codedrobe-adapter-dev
Add, inspect, repair, or validate CodeDrobe Core adapters for Chromium/Electron AI desktop applications. Use when supporting a new app, updating Codex or WorkBuddy compatibility after an app release, discovering installation paths or CDP targets, selecting stable DOM landmarks, adding renderer profiles or…
codex-memory-trim
Manage Codex's native global memory (/.codex/memories) with three sub-procedures - trim (audit + dedupe + three-layer cleanup), compress (rewrite verbose memories into concise form), and add-global (add a custom global rule/preference). Use when the user asks to 精简/清理/整理/压缩 Codex 记忆, 去重, 简化冗长记忆, 添加/写入/修改全局记忆 or a…
CodexClaw
Install and operate a Telegram bot that exposes Codex, MCP, GitHub subagents, repo switching, and minimal frontend dev-server control.
consult
Ask a second AI model (Claude Code or Kimi Code) for an independent opinion on a hard problem in this Home Assistant config. Use when the user asks for a second opinion or another model's view, when two or more of your own attempts at a bug have failed, or before a change that is hard to undo such as editing…
eco-max
Maximum-savings variant of eco - the same frugality rules with a tighter reply budget, for routine chores (rename, small fix, quick lookup, boilerplate). Prefer plain eco for hard or high-stakes work. Works in any language.