القائمة
Integrate anti-hall with oh-my-codex (OMX). Use when the user asks about OMX, omx setup/doctor, Codex workflows, cx.sh, dangerous bypass launch, or activating anti-hall workflows through OMX.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | anti-hall-omx |
| description | Integrate anti-hall with oh-my-codex (OMX). Use when the user asks about OMX, omx setup/doctor, Codex workflows, cx.sh, dangerous bypass launch, or activating anti-hall workflows through OMX. |
OMX is the Codex workflow/orchestration companion. OMC is Claude-focused; for Codex use OMX.
omx --version
omx doctor
Expected active surfaces after omx setup --plugin --scope user --with-mcp --merge-agents:
~/.codex/agents/~/.codex/config.tomlA dangerous-bypass local launcher can be:
#!/bin/bash
omx --madmax "$@"
Resume last run:
./cx.sh resume --last
anti-hall-ship-it plus OMX $plan, $ralplan, $team, $ralph, or $ultragoal as the execution surface when task size justifies it.anti-hall-deadly-loop; debate roles stay on gpt-5.6-sol.anti-hall-context-conserve; route lookup/mechanical work to spark/mini lanes.Anti-hall does not replace OMX. Anti-hall supplies verify-first policy and guards; OMX supplies Codex-native orchestration/workflow runtime.
Explain anti-hall's optional DevSwarm integration from Codex — the hivecontrol reference KB, the (designed, unbuilt) workspace-tier orchestration, and the shipped layered recovery model (Claude-side companion: child self-report → supervisor poke → escalate-to-parent, automatic path NEVER kills, plus the on-demand devswarm-recover CLI — the only kill path). Use when the user asks about DevSwarm, hivecontrol, or the anti-hall liveness supervisor while working in Codex.
Explain and activate anti-hall's optional DevSwarm integration — the hivecontrol reference KB, the (designed, unbuilt) workspace-tier orchestration, and the shipped layered recovery model (child self-report → supervisor poke → escalate-to-parent, automatic path NEVER kills) plus the on-demand devswarm-recover CLI (the only path that ever kills). Use when the user asks "explain the anti-hall DevSwarm integration", "how do I activate the DevSwarm supervisor", "what DevSwarm addons does anti-hall have", "tune the liveness supervisor", "recover a stuck DevSwarm workspace", or anything about hivecontrol / DevSwarm workspaces from an anti-hall angle.
Check or update anti-hall from the local marketplace clone. Use when the user asks to update anti-hall, check whether anti-hall is current, or refresh the Codex port files.
Update anti-hall to the latest released version and show the changelog delta. Use when the user says "update anti-hall", "/anti-hall:update", "upgrade the plugin", "is anti-hall up to date", or "check for an anti-hall update". Fast-forward-pulls the marketplace clone, mirrors the new version into the plugin cache, prints what changed, then has the user reload in-session via /reload-plugins (rarely, a harness build may require a restart — the skill says so when relevant).
Brief the agent that installs or operates anti-hall (in Codex/OMX) on how the whole system works — a DERIVED, live enumeration of every installed hook, the shipped skills, the DevSwarm coordination substrate (mechanical triggers, store, CLI, auto-safe migration), and a docs/KB map. Generated from the real hooks.json and files on disk, never a hardcoded list, so it can't drift. Use when the user asks "brief me on anti-hall", "what's in this build", "how does the whole system work", or when onboarding an agent to install/run anti-hall. For "is it actually installed in Codex / do the guards fire", use anti-hall-doctor.
Brief the agent that installs or operates anti-hall on how the whole system works — a DERIVED, live enumeration of every installed hook (grouped by event, each with its own one-line purpose), the shipped skills, the DevSwarm coordination substrate (mechanical triggers, store, CLI, auto-safe migration), and a docs/KB map. Generated from the actual hooks.json and the files on disk, never a hardcoded list, so it can't drift. Use when the user asks "brief me on anti-hall", "what's in this build", "how does the whole system work", "give me the anti-hall system overview", "what hooks/skills/substrate ship here", or when onboarding an agent to install or run anti-hall. For "is it actually working / do the guards fire", use the `doctor` skill instead.