omx-setuplisted

# 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 ```bash omx setup [--force] [--dry-run] [--verbose] [--scope <user|project>] [--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 - `--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 skills/prompts/agents while keeping setup-owned runtime hooks ## What this setup actually does `omx setup` performs these steps: 1. Resolve setup scope: - `--scope` explicit value - else persisted `./.omx/setup-scope.json` (with automatic migration of legacy values) - else interactive prompt on TTY (default `user`) - else default `user` (safe for CI/tests) 2. If scope is `user`, resolve user skill delivery mode: - explicit `--plugin`, if present - persisted install mode in `./.omx/setup-scope.json`, if present - else discovered installed plugin cache under `${CODEX_HOME:-~/.codex}/plugins/cache/**/.codex-plugin/plugin.json` with `name: oh-my-codex` makes `plugin` the default - else interactive prompt on TTY (`legacy` by default, or `plugin` when a plugin cache is di