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/codexthemes/skills/codex-theme-creatornpx skills add codexthemes/skills --skill codex-theme-creatorgit clone --depth 1 https://github.com/codexthemes/skillsWhat 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.00086 | $0.03863 |
| Opus 5 | $0.00043 | $0.01931 |
| Sonnet 5 | $0.00017 | $0.00773 |
| Haiku 4.5 | $0.00009 | $0.00386 |
Grade A, and why
codex-theme-creator 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a Codex theme
Create a reversible decorative theme without modifying app.asar, the signed app bundle, WindowsApps, user tasks, or authentication data. Preserve native layout and interaction behavior unless the chosen layout mode explicitly permits a bounded composition change.
Authority boundary
Use this skill as the sole design and QA authority for a new Codex theme. Do not read, copy, or combine another installed theme skill, finished theme manifest, finished theme CSS, or local theme collection unless the user explicitly names that source. Do not describe the workflow as combining this skill with “local theme conventions.” Start from this skill's matching skeleton and the user's brief or reference image.
This skill is standalone. Its TypeScript scripts own scaffolding, validation, reversible session application, and restore. Never detect, invoke, read configuration from, or claim a dependency on CodeDrobe, Dream/Fiona, or another theme injector unless the user explicitly asks to use that product. Do not reuse their marker names or runtime data. The only required local tools are Node.js, npx, and the official Codex desktop app.
Managed storage
Keep every generated theme file in the managed library ~/.codexthemes unless the user explicitly requests another location:
- editable source and artwork:
~/.codexthemes/themes/<theme-id>/ - previews:
~/.codexthemes/themes/<theme-id>/previews/ - shareable packages:
~/.codexthemes/exports/ - runtime state:
~/.codexthemes/state/
Never create a staging, scratch, or temporary copy of theme files in or near the current workspace (for example a .codexthemes-stage directory). If the sandbox or permission mode blocks writing to ~/.codexthemes, ask the user to approve writing there instead of writing somewhere else first and moving files later.
Read the required references
Before creating or substantially redesigning a theme, read these files completely:
references/design-playbook.md: layout modes, semantic palette, selectors, and surface coverage.references/qa-checklist.md: real-app acceptance matrix and hard failures.references/theme-schema.md: manifest and portable package contract.references/asset-rights.md: user-material handling and submission handoff.
What ships with it
18 files 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.
- agents/openai.yaml 297 B
- assets/editorial-showcase.css 3.2 KB
- assets/native-background.css 1.6 KB
- assets/native-immersive.css 10 KB
- assets/palette-only.css 2.7 KB
- references/asset-rights.md 852 B
- references/design-playbook.md 13 KB
- references/qa-checklist.md 5.3 KB
- references/theme-schema.md 3.8 KB
- scripts/apply-theme.ts 24 KB runs code
- scripts/export-theme.ts 5.5 KB runs code
- scripts/paths.ts 611 B runs code
- scripts/qa-contrast.ts 11 KB runs code
- scripts/readability.ts 8.8 KB runs code
- scripts/scaffold-theme.ts 6.7 KB runs code
- scripts/self-test.ts 5.5 KB runs code
- scripts/validate-skill.ts 3.6 KB runs code
- scripts/validate-theme.ts 10 KB runs code
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 · 232 lines · 86 tokens per session scan A 1c76ed35931f
codex-theme-creator is a skill published in the GitHub repository codexthemes/skills (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 86 tokens to every session and 3,863 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…