Borrowing it
Nothing to install: this file belongs to Orinks/AccessiWeather. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Orinks/AccessiWeather/main/.codex/skills/omx-setup/SKILL.mdgit clone --depth 1 https://github.com/Orinks/AccessiWeatherWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/orinks/accessiweather/omx-setup)<a href="https://agentmods.dev/skills/orinks/accessiweather/omx-setup"><img src="https://agentmods.dev/badge/skills/orinks/accessiweather/omx-setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/orinks/accessiweather/omx-setup"><img src="https://agentmods.dev/badge/skills/orinks/accessiweather/omx-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00021 | $0.02147 |
| Opus 5.5 | $0.00008 | $0.00859 |
| Sonnet 5.5 | $0.00004 | $0.00429 |
| Haiku 4.5 | $0.00002 | $0.00215 |
Grade B, and why
omx-setup scanned grade B with 1 finding 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
| `~/.codex/config.toml` / `./.codex/config.toml` | `omx setup` generated blocks + user edits | Setup refreshes OMX-managed blocks while preserving supported manual content. | How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OMX Setup
Use this skill when users want to install or refresh oh-my-codex for the current project plus user-level OMX directories.
Command
omx setup [--force] [--merge-agents] [--dry-run] [--verbose] [--scope <user|project>] [--plugin|--legacy|--install-mode <legacy|plugin>]
If you only want lightweight AGENTS.md scaffolding for an existing repo or subtree, use omx agents-init [path] instead of full setup.
Supported setup flags (current implementation):
--force: overwrite/reinstall managed artifacts where applicable--merge-agents: whenAGENTS.mdalready exists, preserve user-authored content and insert/refresh OMX-managed generated sections between explicit<!-- OMX:AGENTS:START -->/<!-- OMX:AGENTS:END -->markers--dry-run: print actions without mutating files--verbose: print per-file/per-step details--scope: choose install scope (user,project)--plugin: use Codex plugin delivery for bundled skills while archiving/removing legacy OMX-managed prompts/native agents and keeping setup-owned runtime hooks--legacy: use legacy setup delivery, overriding any persisted plugin install mode--install-mode: explicitly choose setup delivery mode (legacyorplugin); canonical form for scripted setup
What this setup actually does
omx setup performs these steps:
- Resolve setup scope:
--scopeexplicit value- else persisted
./.omx/setup-scope.json(with automatic migration of legacy values) - if a TTY user has persisted setup preferences,
omx setupfirst summarizes the recorded choices and asks whether to keep, review/change, or reset them - else interactive prompt on TTY (default
user) - else default
user(safe for CI/tests)
- If scope is
user, resolve user skill delivery mode:- explicit
--plugin,--legacy, or--install-mode legacy|plugin, if present - persisted install mode in
./.omx/setup-scope.json, if present and the TTY review decision iskeep - else discovered installed plugin cache under
${CODEX_HOME:-~/.codex}/plugins/cache/**/.codex-plugin/plugin.jsonwithname: oh-my-codexmakespluginthe default - else interactive prompt on TTY (
legacyby default, orpluginwhen a plugin cache is discovered) - else default
legacyunless a plugin cache is discovered
- explicit
- Create directories and persist effective scope/install mode
- In legacy mode, install prompts/native agents/skills and merge full config.toml. In plugin mode, archive/remove legacy OMX-managed prompts/native agents/skills but keep native Codex hooks installed.
- Verify Team CLI API interop markers exist in built
dist/cli/team.js - Generate AGENTS.md defaults only when selected/allowed (or legacy behavior outside plugin mode)
- Configure notify hook references outside plugin mode and write
./.omx/hud-config.json
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.
- 1mo ago First seen · 136 lines · 21 tokens per session scan B 3232d6d38a6a
omx-setup is a skill published in the GitHub repository Orinks/AccessiWeather (24 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 2,147 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.