Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add IAPro-Community/Orquestrador-Maestro --skill cancelgit clone --depth 1 https://github.com/IAPro-Community/Orquestrador-MaestroWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/iapro-community/orquestrador-maestro/cancel)<a href="https://agentmods.dev/skills/iapro-community/orquestrador-maestro/cancel"><img src="https://agentmods.dev/badge/skills/iapro-community/orquestrador-maestro/cancel/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/iapro-community/orquestrador-maestro/cancel"><img src="https://agentmods.dev/badge/skills/iapro-community/orquestrador-maestro/cancel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00035 | $0.04238 |
| Opus 5 | $0.00017 | $0.02119 |
| Sonnet 5 | $0.00007 | $0.00848 |
| Haiku 4.5 | $0.00003 | $0.00424 |
Grade C, and why
cancel scanned grade C with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
2. Remove team state directory: rm -rf .omx/state/team/{name}/ Copies of this mod
1 near-identical copy found in the catalogue:
- cancel — 97% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cancel Skill
Intelligent cancellation that detects and cancels the active OMX mode.
The cancel skill is the standard way to complete and exit any OMX mode.
When the stop hook detects work is complete, it instructs the LLM to invoke
this skill for proper state cleanup. If cancel fails or is interrupted,
retry with --force flag, or wait for the 2-hour staleness timeout as
a last resort.
What It Does
Automatically detects which mode is active and cancels it:
- Autopilot: Stops workflow, preserves progress for resume
- Ralph: Stops persistence loop, clears linked ultrawork if applicable
- Ultrawork: Stops parallel execution (standalone or linked)
- Ecomode: Stops token-efficient parallel execution (standalone or linked to ralph)
- UltraQA: Stops QA cycling workflow
- Swarm: Stops coordinated agent swarm, releases claimed tasks
- Ultrapilot: Stops parallel autopilot workers
- Pipeline: Stops sequential agent pipeline
- Team: Sends shutdown inbox to all workers, waits for exit, kills tmux session, and clears team state
Usage
/cancel
Or say: "cancelomc", "stopomc"
Auto-Detection
/cancel follows the session-aware state contract:
- By default the command inspects the current session via
state_list_activeandstate_get_status, navigating.omx/state/sessions/{sessionId}/…to discover which mode is active. - When a session id is provided or already known, that session-scoped path is authoritative. Legacy files in
.omx/state/*.jsonare consulted only as a compatibility fallback if the session id is missing or empty. - Swarm is a shared SQLite/marker mode (
.omx/state/swarm.db/.omx/state/swarm-active.marker) and is not session-scoped. - The default cleanup flow calls
state_clearwith the session id to remove only the matching session files; modes stay bound to their originating session.
Normative Ralph cancellation post-conditions (MUST)
For Ralph-targeted cancellation (standalone or linked), completion is defined by post-conditions:
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 400 lines · 35 tokens per session scan C a8dea77274d0
cancel is a skill published in the GitHub repository IAPro-Community/Orquestrador-Maestro (42 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 4,238 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
dry-run
Preview command effects without making changes. Simulates file writes, git operations, agent spawns, and state changes. All reads execute normally for accurate preview. Use --dry-run flag on any command.
finalize-phase
Completes feature/epic workflows after deployment with comprehensive walkthrough generation for epics (v5.0+), roadmap updates, artifact archival, documentation, and branch cleanup. Use after /ship-prod, /deploy-prod, or /build-local completes, or when user asks to finalize. (project).
task-breakdown-phase
Standard Operating Procedure for /tasks phase. Covers task sizing, acceptance criteria definition, and TDD-first task sequencing. (project).
staging-deployment-phase
Deploys features to staging environment with database migrations, health checks, and deployment verification. Use during /ship-staging phase or when deploying to staging environments for validation before production release.
dependency-conflict-resolver
Detect and resolve package dependency conflicts before installation across npm/yarn/pnpm, pip/poetry, cargo, and composer. Auto-trigger when installing/upgrading packages. Validates peer dependencies, version compatibility, security vulnerabilities. Auto-resolves safe conflicts (patches, dev deps), suggests manual…