omx-setup — community omx-setup, oh-my-codex, community, ide skills, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

About this Skill

Ideal for Advanced AI Agents requiring seamless integration with OpenAI Codex CLI, such as Cursor, Windsurf, or Claude Code, for efficient project setup and management. OmX - Oh My Codex: Power tools for OpenAI Codex CLI

Yeachan-Heo Yeachan-Heo
[0]
[0]
Updated: 3/5/2026

Agent Capability Analysis

The omx-setup skill by Yeachan-Heo is an open-source community AI agent skill for Claude Code and other IDE workflows, helping agents execute tasks with better context, repeatability, and domain-specific guidance.

Ideal Agent Persona

Ideal for Advanced AI Agents requiring seamless integration with OpenAI Codex CLI, such as Cursor, Windsurf, or Claude Code, for efficient project setup and management.

Core Value

Empowers agents to effortlessly install or refresh oh-my-codex for current projects and user-level OMX directories, utilizing flags like --force, --dry-run, and --verbose for customized setup experiences, and supporting scopes such as user or project.

↓ Capabilities Granted for omx-setup

Automating oh-my-codex installation for new projects
Refreshing OMX directories for updated configurations
Dry-running setup commands for testing purposes without mutating files

! Prerequisites & Limits

  • Requires OpenAI Codex CLI access
  • Limited to oh-my-codex tooling
  • Scope limited to user or project level
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

omx-setup

Install omx-setup, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md
Readonly

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
1omx setup [--force] [--dry-run] [--verbose] [--scope <user|project>]

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)

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. Create directories and persist effective scope
  3. Install prompts, native agent configs, skills, and merge config.toml (scope determines target directories)
  4. Verify Team CLI API interop markers exist in built dist/cli/team.js
  5. Generate project-root ./AGENTS.md from templates/AGENTS.md (or skip when existing and no force)
  6. Configure notify hook references and write ./.omx/hud-config.json

Important behavior notes

  • omx setup only prompts for scope when no scope is provided/persisted and stdin/stdout are TTY.
  • Local project orchestration file is ./AGENTS.md (project root).
  • If AGENTS.md exists and --force is not used, interactive TTY runs ask whether to overwrite. Non-interactive runs preserve the file.
  • Scope targets:
    • user: user directories (~/.codex, ~/.agents/skills, ~/.omx/agents)
    • project: local directories (./.codex, ./.agents/skills, ./.omx/agents)
  • If persisted scope is project, omx launch automatically uses CODEX_HOME=./.codex unless user explicitly overrides CODEX_HOME.
  • With --force, AGENTS overwrite may still be skipped if an active OMX session is detected (safety guard).
  • Legacy persisted scope values (project-local) are automatically migrated to project with a one-time warning.
  1. Run setup:
bash
1omx setup --force --verbose
  1. Verify installation:
bash
1omx doctor
  1. Start Codex with OMX in the target project directory.

Expected verification indicators

From omx doctor, expect:

  • Prompts installed (scope-dependent: user or project)
  • Skills installed (scope-dependent: user or project)
  • AGENTS.md found in project root
  • .omx/state exists
  • OMX MCP servers configured in scope target config.toml (~/.codex/config.toml or ./.codex/config.toml)

Troubleshooting

  • If using local source changes, run build first:
bash
1npm run build
  • If your global omx points to another install, run local entrypoint:
bash
1node bin/omx.js setup --force --verbose
2node bin/omx.js doctor
  • If AGENTS.md was not overwritten during --force, stop active OMX session and rerun setup.

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is omx-setup?

Ideal for Advanced AI Agents requiring seamless integration with OpenAI Codex CLI, such as Cursor, Windsurf, or Claude Code, for efficient project setup and management. OmX - Oh My Codex: Power tools for OpenAI Codex CLI

How do I install omx-setup?

Run the command: npx killer-skills add Yeachan-Heo/oh-my-codex. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for omx-setup?

Key use cases include: Automating oh-my-codex installation for new projects, Refreshing OMX directories for updated configurations, Dry-running setup commands for testing purposes without mutating files.

Which IDEs are compatible with omx-setup?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for omx-setup?

Requires OpenAI Codex CLI access. Limited to oh-my-codex tooling. Scope limited to user or project level.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add Yeachan-Heo/oh-my-codex. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use omx-setup immediately in the current project.

Related Skills

Looking for an alternative to omx-setup or another community skill for your workflow? Explore these related open-source skills.

View All

widget-generator

Logo of f
f

f.k.a. Awesome ChatGPT Prompts. Share, discover, and collect prompts from the community. Free and open source — self-host for your organization with complete privacy.

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

flags is a Next.js feature management skill that enables developers to efficiently add or modify framework feature flags, streamlining React application development.

★ 138.4k
⑂ 0
Browser

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

★ 72.8k
⑂ 0
AI

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

★ 72.8k
⑂ 0
AI