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/zereight/gitlab-mcp/cancelnpx skills add zereight/gitlab-mcp --skill cancelgit clone --depth 1 https://github.com/zereight/gitlab-mcpWrote 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/zereight/gitlab-mcp/cancel)<a href="https://agentmods.dev/skills/zereight/gitlab-mcp/cancel"><img src="https://agentmods.dev/badge/skills/zereight/gitlab-mcp/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 | $0.00037 | $0.00736 |
| Opus 5 | $0.00018 | $0.00368 |
| Sonnet 5 | $0.00007 | $0.00147 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
cancel scanned grade A with 0 findings 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 4d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cancel
Intelligent cancellation that detects and cancels the active OMG mode.
What It Does
Automatically detects which mode is active and cancels it:
- OMG Autopilot: Stops workflow, preserves progress for resume
- Ralph: Stops persistence loop
- Ultrawork: Stops parallel execution
- UltraQA: Stops QA cycling workflow
- Team: Sends shutdown to all teammates, cleans up
- Self-Improve: Stops loop, preserves iteration state for resume
Usage
/cancel
/cancel --force
/cancel --all
Auto-Detection
Reads .omc/state/ to discover which mode is active. Cancels in dependency order:
- OMG Autopilot (includes linked ralph/ultraqa cleanup)
- Ralph (cleans linked ultrawork)
- Ultrawork (standalone)
- UltraQA (standalone)
- Team (graceful shutdown + cleanup)
- Self-Improve (preserve iteration state)
Workflow
1. Parse Arguments
Check for --force or --all flags.
2. Detect Active Modes
Use omg_read_state to check each mode's state file.
3A. Force Mode (--force or --all)
Clear ALL state files in .omc/state/. Nuclear option.
3B. Smart Cancellation (default)
If OMG Autopilot Active
- Check for linked ralph → clear ultrawork if linked → clear ralph
- Check for linked ultraqa → clear it
- Mark omg-autopilot inactive (preserve state for resume)
If Ralph Active (not OMG Autopilot)
- Check for linked ultrawork → clear if linked
- Clear ralph state
If Team Active
- Signal shutdown to all teammates
- Wait for responses (15s timeout per member)
- Clean up team resources
- Clear linked ralph if present
If UltraQA / Ultrawork / Self-Improve Active
Clear state directly.
No Active Modes
Report: "No active OMG modes detected. Use --force to clear all state."
What Gets Preserved
| Mode | State Preserved | Resume Command |
|---|---|---|
| OMG Autopilot | Yes (phase, files, spec) | /omg-autopilot |
| Self-Improve | Yes (iteration state) | /self-improve --resume |
| Ralph | No | N/A |
| Others | No | N/A |
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.
- 4d ago First seen · 98 lines · 37 tokens per session scan A a957d2c23089
cancel is a skill published in the GitHub repository zereight/gitlab-mcp (1,939 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 736 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…