omx-setup

Automate oh-my-codex installation and configuration across user and project scopes.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/YeaChan05/Remittance --skill omx-setup-yeachan05
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omx-setup
Source: https://github.com/YeaChan05/Remittance/tree/main/.codex/skills/omx-setup
Command: npx skills add https://github.com/YeaChan05/Remittance --skill omx-setup-yeachan05

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OMX Setup installs and configures oh-my-codex across the target project and user environments, ensuring consistent configuration and hooks.

Core Features & Use Cases

  • Resolve scope (user or project) and resolve skill delivery mode.
  • Create and persist configuration artifacts such as AGENTS.md and hud-config.json.
  • Support legacy and plugin delivery modes, merging or archiving as needed, and verify integration points.

Quick Start

Run omx setup --force --verbose to install or refresh OMX for your current scope.

Frequently Asked Questions about omx-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate oh-my-codex configuration setup across multiple project scopes?

Automating oh-my-codex configuration setup is handled by resolving the target scope, selecting a delivery mode, and generating artifacts like AGENTS.md and hud-config.json across your local directories. It validates and persists scope settings to ensure consistent configuration.

What is the best way to refresh OMX configuration and update legacy prompts?

Refreshing OMX configuration involves merging or archiving legacy prompts based on your resolved delivery mode. The process updates outdated configuration files, validates integration points, and verifies setup notifications to maintain a consistent environment.

Can I install oh-my-codex configuration for both user and project environments?

Yes, installing oh-my-codex configuration supports both user and project environments. The setup process validates and persists the selected scope, ensuring that configuration artifacts and hooks are correctly applied to the appropriate local directories.

Do I need to manually create AGENTS.md and hud-config.json files during setup?

No, you do not need to manually create AGENTS.md or hud-config.json files. The setup automation generates these configuration artifacts automatically based on your resolved scope and delivery mode, ensuring proper integration points and hooks.

Why does my oh-my-codex setup fail to verify integration points and hooks?

Setup verification fails when legacy prompts conflict with the selected delivery mode or when scope persistence is interrupted. Running a force refresh with verbose logging archives outdated prompts and validates integration points to resolve configuration hook errors.