Loading...
Loading...
Expert in Oh My Codex (OMX) - workflow layer for OpenAI Codex CLI with agents, skills, and team coordination
npx skill4agent add aradotso/codex-skills oh-my-codex-workflowSkill by ara.so — Codex Skills collection.
$deep-interview$ralplan$ralph$team.omx/$deep-interview$ralplan$team$ralphAGENTS.md.codex/hooks.jsonnpm install -g @openai/codexcodex login statustmux# Install both Codex CLI and OMX globally
npm install -g @openai/codex oh-my-codex
# Run setup to install prompts, skills, hooks, and scaffolding
omx setup
# Verify installation
omx doctor
# Smoke test actual Codex execution
omx exec --skip-git-repo-check -C . "Reply with exactly OMX-EXEC-OK"# Check npm, install latest, and refresh setup
omx update
# Or manually:
npm install -g oh-my-codex
omx setup# 1. Launch OMX with recommended settings
omx --madmax --high
# Inside the Codex session:
# 2. Clarify scope (when boundaries are unclear)
$deep-interview "clarify the authentication change"
# 3. Create and approve implementation plan
$ralplan "approve the auth plan and review tradeoffs"
# 4a. Execute with persistent completion loop
$ralph "carry the approved plan to completion"
# OR 4b. Execute with coordinated parallel team
$team 3:executor "execute the approved plan in parallel"
# 5. Convert to durable goals (for multi-session work)
$ultragoal "turn this launch into durable Codex goals"# Default: auto-managed tmux on macOS/Linux interactive terminals
omx --madmax --high
# Direct mode (no OMX tmux/HUD management)
omx --direct --yolo
# Set persistent preference via environment
export OMX_LAUNCH_POLICY=direct # or tmux, detached-tmux, auto
omx --yolo
# CLI flags override environment (last flag wins)
OMX_LAUNCH_POLICY=direct omx --tmux --yolo # Uses tmux$deep-interview "clarify requirements for the new API endpoint"
$deep-interview "understand the performance bottleneck before planning fixes"$ralplan "approve the implementation plan and review tradeoffs"
$ralplan "verify the migration strategy is safe"$ralph "carry the approved plan to completion"
$ralph "implement the auth changes with verification"# Launch team with N agents of role:type
$team 3:executor "execute the approved plan in parallel"
$team 2:architect "design the new service architecture"
# Team management (CLI, not in-session)
omx team status <team-name>
omx team resume <team-name>
omx team shutdown <team-name>$ultragoal "turn this migration into sequential Codex goals".omx/
├── plans/ # Approved implementation plans from $ralplan
├── logs/ # Execution logs from $ralph and $team
├── memory/ # Persistent agent memory
├── ultragoal/ # Durable multi-goal artifacts
└── teams/ # Team runtime state and worktrees
.codex/
├── config.toml # Codex configuration (OMX seeds defaults)
├── hooks.json # Native Codex hooks (OMX-managed wrappers)
└── prompts/ # OMX-installed role and skill prompts
AGENTS.md # Project-specific agent guidance (optional).omx-config.json{
"model": "gpt-5.5",
"provider": "openai",
"baseURL": "https://api.openai.com/v1",
"env": {
"OPENAI_API_KEY": "${OPENAI_API_KEY}"
}
}.codex/config.tomlgpt-5.5[gpt-5.5]
model_name = "gpt-5.5"
model_context_window = 250000
model_auto_compact_token_limit = 200000# Merge mode: inserts between <!-- OMX:AGENTS:START --> / END -->
omx setup --merge-agents
# Default: skips existing AGENTS.md in non-interactive mode
omx setup// TypeScript example: typical OMX workflow pattern
async function standardWorkflow() {
// 1. Clarify scope
// Run: $deep-interview "understand the feature requirements"
// 2. Create plan
// Run: $ralplan "approve the implementation approach"
// 3. Execute
// Option A - single persistent owner:
// Run: $ralph "implement with verification"
// Option B - parallel team:
// Run: $team 3:executor "execute in parallel"
// 4. Convert to goals for multi-session work
// Run: $ultragoal "create durable goals for remaining work"
}# Launch team from CLI
omx team 3:executor "migrate database schema with verification"
# Check team status
omx team status migration-team
# Resume paused team
omx team resume migration-team
# Clean shutdown
omx team shutdown migration-team// Use omx exec for one-off Codex calls outside a session
import { execSync } from 'child_process';
const result = execSync(
'omx exec --skip-git-repo-check -C . "List all TypeScript files in src/"',
{ encoding: 'utf-8' }
);
console.log(result);# Skills are stored in .codex/prompts/skills/
# Create a new skill file:
# .codex/prompts/skills/my-custom-skill.md
# Content structure:
# ---
# name: my-custom-skill
# triggers:
# - do custom thing
# ---
# # Skill instructions
# When invoked, this skill should...omx setup # Install prompts, skills, hooks, scaffolding
omx setup --merge-agents # Preserve existing AGENTS.md while adding OMX sections
omx setup --force # Force overwrite existing files
omx doctor # Verify installation integrity
omx update # Check npm, install latest, refresh setup
omx uninstall # Remove OMX-managed hooks (keep user hooks)omx --madmax --high # Recommended default
omx --yolo # Quick launch, less safety
omx --direct --yolo # No OMX tmux management
omx --tmux # Force tmux modeomx exec [options] "prompt" # Direct Codex execution
omx exec --skip-git-repo-check -C . "prompt" # Skip git repo requirementomx team N:role "task" # Launch N agents of role:type
omx team status <name> # Check team status
omx team resume <name> # Resume paused team
omx team shutdown <name> # Clean shutdown
omx team list # List active teamsomx hud --watch # Launch monitoring HUD (operator surface)# Launch policy preference
export OMX_LAUNCH_POLICY=direct # direct, tmux, detached-tmux, auto
# Codex home (affects plugin cache location)
export CODEX_HOME=~/.codex
# API keys (referenced in .omx-config.json)
export OPENAI_API_KEY=your_key_here
export ANTHROPIC_API_KEY=your_key_here# Verify setup
omx doctor
# Check Codex auth
codex login status
# Smoke test actual execution
omx exec --skip-git-repo-check -C . "Reply with exactly OMX-EXEC-OK"
# Refresh setup after version bump
omx setup
# Or use update to check npm first
omx update# Verify tmux is installed
which tmux
# Check team status
omx team status <team-name>
# Review team logs
cat .omx/teams/<team-name>/logs/*
# Clean shutdown if stuck
omx team shutdown <team-name># Verify hooks are registered
cat .codex/hooks.json
# Refresh OMX-managed hooks (preserves user hooks)
omx setup
# Check hook execution logs
cat .omx/logs/hooks/*# Verify .omx-config.json routing
cat .omx-config.json
# Check Codex config
cat .codex/config.toml
# Test with direct exec
omx exec --skip-git-repo-check -C . "test prompt"
# Verify env vars are set
echo $OPENAI_API_KEYnpm install -g @openai/codexcodex login
codex login status# macOS
brew install tmux
# Linux
sudo apt-get install tmux # or yum, dnf, etc.# Use merge mode to preserve existing content
omx setup --merge-agents
# Or force overwrite
omx setup --forcenpm install -g oh-my-codex
omx setup.codex/hooks.json.codex/prompts/agents/---
name: security-reviewer
role: Security Review Specialist
---
# Security Reviewer Agent
You are a security review specialist. When assigned a task:
1. Review code for security vulnerabilities
2. Check for OWASP top 10 issues
3. Validate input sanitization
4. Review authentication/authorization
5. Document findings with severity levels# Use OMX in CI/CD
omx exec --skip-git-repo-check -C . "Run security audit on changed files"
# Integrate with git hooks
# .git/hooks/pre-commit
#!/bin/bash
omx exec -C . "Review staged changes for issues"$deep-interview$ralplan$ralph$team$ultragoal.omx/omx doctoromx exec