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/jinxlzc/grok-codex-plugin/cancelgit clone --depth 1 https://github.com/jinxlzc/grok-codex-pluginWrote 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/commands/jinxlzc/grok-codex-plugin/cancel)<a href="https://agentmods.dev/commands/jinxlzc/grok-codex-plugin/cancel"><img src="https://agentmods.dev/badge/commands/jinxlzc/grok-codex-plugin/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.00010 | $0.00070 |
| Opus 5 | $0.00005 | $0.00035 |
| Sonnet 5 | $0.00002 | $0.00014 |
| Haiku 4.5 | $0.00001 | $0.00007 |
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 5d 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.
What it actually says
!node "${GROK_PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.mjs" cancel "$ARGUMENTS"
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.
- 5d ago First seen · 9 lines · 10 tokens per session scan A 7f642ff9cc06
cancel is a command published in the GitHub repository jinxlzc/grok-codex-plugin (1 stars, last pushed 22d ago), licensed Apache-2.0. It adds 10 tokens to every session and 70 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
delegate
Delegate investigation, an explicit fix request, or follow-up work to the Grok delegate subagent.
review
Run a Grok code review against local git state.
login
Sign in to Grok Build CLI using the default install path.
critique
Run a Grok Build critique that challenges the implementation approach and design choices.
check
Check whether the local Grok Build CLI is ready for the Claude Code bridge.
review
Run a read-only Grok code review against local git state.