Cancel any active OMX mode (autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, team)
62
72%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Medium
Suggest reviewing before use
Fix and improve this skill with Tessl
tessl review fix ./plugins/oh-my-codex/skills/cancel/SKILL.mdThe canonical home for this skill is cancel in Yeachan-Heo/oh-my-codex
Use /cancel (or cancelomc / stopomc) to stop an active OMX mode and perform its documented cleanup. Read AGENTS.md#durable-runtime-invariants-canonical-ssot first; it is the invariant authority for scope, ownership, hooks, and Team cleanup.
/cancel and /cancel --force.--all, unknown flags, repeated flags, and mixed flags before mutation.omx state list-active --json
omx state get-status --mode <mode> --jsonautopilot → ralph → ultrawork → ecomode → ultraqa → swarm → ultrapilot → pipeline → team → plan-consensus.active:false, current_phase:"cancelled", completed_at) and terminalize a proven linked Ultrawork/Ecomode state in the same scope. Confirm the post-conditions in docs/contracts/ralph-cancel-contract.md.omx team status <team> --json; use omx team shutdown <team> after the normal completion gate, or follow the explicit abort path.omx state clear --input '{"mode":"<mode>","session_id":"<session>"}' --json--force, perform its documented native-stop cleanup. Report rollback or cleanup failures rather than claiming success.Report one result per selected mode: mode, scope/session, terminal phase, preserved state, linked cleanup, and any refusal reason. A clean no-op reports No active OMX modes detected. Include Team status and shutdown evidence when Team was selected.
304fb3b
Canonical home
since Sep 10, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.