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 agentmods add skills/orinks/accessiweather/cancelnpx skills add Orinks/AccessiWeather --skill cancelgit clone --depth 1 https://github.com/Orinks/AccessiWeatherWrote 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/orinks/accessiweather/cancel)<a href="https://agentmods.dev/skills/orinks/accessiweather/cancel"><img src="https://agentmods.dev/badge/skills/orinks/accessiweather/cancel.svg" alt="Measured on agentmods" 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.00039 | $0.04242 |
| Opus 5 | $0.00019 | $0.02121 |
| Sonnet 5 | $0.00008 | $0.00848 |
| Haiku 4.5 | $0.00004 | $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 6d 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}/ This is a copy
97% identical to cancel — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 6d ago First seen · 400 lines · 39 tokens per session scan C f98dc70c8873
cancel is a skill published in the GitHub repository Orinks/AccessiWeather (24 stars, last pushed 12d ago), licensed MIT. It adds 39 tokens to every session and 4,242 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 97% identical to cancel, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…