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 commands/limeflash/antigravity-plugin-cc/cancelgit clone --depth 1 https://github.com/limeflash/antigravity-plugin-ccWhat 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.00021 | $0.00258 |
| Opus 5 | $0.00010 | $0.00129 |
| Sonnet 5 | $0.00004 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
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 yesterday.
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.
What it actually says
Stop an active background job started by /agy:rescue --background.
Defaults to the latest cancelable job in this workspace.
How to invoke
$ARGUMENTS
If empty:
node "${CLAUDE_PLUGIN_ROOT}/scripts/agy-companion.mjs" cancel
If the user passed an id or prefix:
node "${CLAUDE_PLUGIN_ROOT}/scripts/agy-companion.mjs" cancel "<id-or-prefix>"
Behavior notes
- The companion sends
SIGTERMfirst, waits up to 5 seconds, then escalates toSIGKILLif the process hasn't exited. On Windows, this is whatever the OS provides for those signals. - A job whose record claims
runningbut whose PID is already dead is markedcanceledwithout sending any signal. - A completed/failed/already-canceled job exits 2 with a message saying nothing was done — there's nothing to cancel.
Return the companion's stdout verbatim.
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.
- yesterday First seen · 39 lines · 21 tokens per session scan A 665891e15acb
cancel is a command published in the GitHub repository limeflash/antigravity-plugin-cc (2 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 258 once invoked, about $0.0001 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.