Are agent themes safe? Mostly — here's the ladder.
"Theme" covers three very different mechanisms, and they don't share a risk profile. Every item on CodexSkins is labeled with one of these tiers, so you always know which layer of your setup you're trusting.
Color-token themes (our entire theme catalog)
A list of hex colors applied through the agent's own appearance settings — the same thing you'd do by hand in Settings → Appearance or /theme. No code runs, nothing is downloaded, no files outside appearance config are touched. Worst case: ugly colors. Revert by switching back to a built-in theme.
Settings-file edits
Some looks are applied by editing config files (statusline scripts, terminal profiles). Safe when you can read the diff first — which is why our install prompts require the agent to report every change it makes. Only paste config snippets you understand or that your agent explains back to you.
CDP / DOM-injection skins (anime wallpaper skins, pets)
Full visual skins for desktop agent apps typically work by attaching to the app through a local debugging channel (Chrome DevTools Protocol) and injecting CSS/images. Done well it's local-only and reversible — but the mechanism can read what's on screen, so only run open-source engines you (or your agent) have reviewed, bound to 127.0.0.1, and prefer one-click-restore tooling. We don't distribute injection engines; when we link to skin ecosystems, we label them with this tier.
Why our install prompts are written the way they are
Every "Copy install prompt" on this site ends with the same three rules: change appearance settings only, keep contrast readable, and report back everything you touched. That turns your agent into the audit log — you see exactly what changed, and reverting is one more sentence. No downloads, no scripts, no API keys involved.
Questions? Start with the theme gallery or read the install guides.