Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add LovelaceLoom/grok-plugin-cc/plugin install grokWrote 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/lovelaceloom/grok-plugin-cc/rescue)<a href="https://agentmods.dev/commands/lovelaceloom/grok-plugin-cc/rescue"><img src="https://agentmods.dev/badge/commands/lovelaceloom/grok-plugin-cc/rescue/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/commands/lovelaceloom/grok-plugin-cc/rescue"><img src="https://agentmods.dev/badge/commands/lovelaceloom/grok-plugin-cc/rescue.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.00020 | $0.00613 |
| Opus 5.5 | $0.00008 | $0.00245 |
| Sonnet 5.5 | $0.00004 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
rescue 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 1mo 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
Invoke the grok:grok-rescue subagent via the Agent tool (subagent_type: "grok:grok-rescue"), forwarding the raw user request as the prompt.
The final user-visible response must be Grok's output verbatim.
Raw user request: $ARGUMENTS
Execution mode:
- If the request includes
--background, run thegrok:grok-rescuesubagent in the background. - If the request includes
--wait, run thegrok:grok-rescuesubagent in the foreground. - If neither flag is present, default to foreground for a small, clearly bounded request, and background for anything open-ended or multi-step.
--backgroundand--waitare execution flags for Claude Code. Do not forward them to the companion'stasksubcommand, and do not treat them as part of the natural-language task text.--writeand--read-onlyare runtime-selection flags. Preserve them for the forwardedtaskcall.--model,--effort,--session-id,--resume=<id>/--resume, and--continueare runtime-selection flags. Preserve them for the forwardedtaskcall.
Operating rules:
- The subagent is a thin forwarder only. It should use one
Bashcall to invokenode "${CLAUDE_PLUGIN_ROOT}/scripts/companion.mjs" task ...and return that command's stdout as-is. - Default to read-only Grok behavior. Add
--writeonly if the user explicitly asks for code changes or fixes to be applied. - Return the companion's stdout verbatim to the user.
- Do not paraphrase, summarize, rewrite, or add commentary before or after it.
- Do not ask the subagent to inspect files, monitor progress, poll
/grok:status, fetch/grok:result, call/grok:cancel, summarize output, or do follow-up work of its own. - Do not call
review,adversarial-review,status,result, orcancel. This subagent only forwards totask. - If the helper reports that Grok is missing or unauthenticated, stop and tell the user to run
/grok:setup. - If the user did not supply a request, ask what Grok should investigate or fix.
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.
- 1mo ago First seen · 32 lines · 20 tokens per session scan A 50c4e13e1375
rescue is a command published in the GitHub repository LovelaceLoom/grok-plugin-cc (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 613 once invoked, about $0.0001 per session on Opus 5.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
ia-verify
Run pre-PR verification chain: build, types, lint, tests, security scan, diff review.
announce
Draft X/Twitter announcement post (or thread) for the latest plugin release.
orchestrate
Do this task as an orchestrator. The aim is the same result at a fraction of the cost: in a long session, every token in this conversation is re-read on each later request, while a subagent's reading is discarded when it returns. The plugin's subagents run on Haiku 5.5, about 40× cheaper per token than Opus 5.5.
release
Generate changelog, bump version, and create git tag.
render
Inspect an archived transcript (gzipped) — show counts, tool calls, errors. Useful after a PreCompact or SessionEnd, before deciding to write a retroactive /continuum:checkpoint.
playbook
Manage Mochi playbooks (list, show, run, delete). Plays through the browser MCP tools.