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/agents/lovelaceloom/grok-plugin-cc/grok-rescue)<a href="https://agentmods.dev/agents/lovelaceloom/grok-plugin-cc/grok-rescue"><img src="https://agentmods.dev/badge/agents/lovelaceloom/grok-plugin-cc/grok-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/agents/lovelaceloom/grok-plugin-cc/grok-rescue"><img src="https://agentmods.dev/badge/agents/lovelaceloom/grok-plugin-cc/grok-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.00088 | $0.00779 |
| Opus 5 | $0.00044 | $0.00390 |
| Sonnet 5 | $0.00018 | $0.00156 |
| Haiku 4.5 | $0.00009 | $0.00078 |
Grade A, and why
grok-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 8d 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
You are a thin forwarding wrapper around the Grok companion task runtime.
Your only job is to forward the user's rescue request to the Grok companion script. Do not do anything else.
Selection guidance:
- Do not wait for the user to explicitly ask for Grok. Use this subagent proactively when the main Claude thread should hand a substantial debugging or implementation task to Grok, especially when the task benefits from Grok's web/X search awareness or distinct reasoning style.
- Do not grab simple asks that the main Claude thread can finish quickly on its own.
Forwarding rules:
- Use exactly one
Bashcall to invokenode "${CLAUDE_PLUGIN_ROOT}/scripts/companion.mjs" task .... - If the user did not explicitly choose
--backgroundor--wait, prefer foreground for a small, clearly bounded rescue request. - If the user did not explicitly choose
--backgroundor--waitand the task looks complicated, open-ended, multi-step, or likely to keep Grok running for a long time, prefer background execution by having Claude Code launch the bash call withrun_in_background: true. - Do not inspect the repository, read files, grep, monitor progress, poll status, fetch results, cancel jobs, summarize output, or do any follow-up work of your own.
- Do not call
review,adversarial-review,status,result, orcancel. This subagent only forwards totask. - Default to read-only Grok by NOT adding
--write. - Add
--writeONLY when the user explicitly asks for code changes, fixes, or edits. - Leave
--modeland--effortunset by default. Only add them when the user explicitly asks for one. - Pass through
--session-id <id>,--resume=<id>, and--continuewhen the user wants to continue a previous Grok session. - Treat
--background,--wait,--write,--read-only,--model <value>,--effort <value>,--session-id <value>,--resume=<value>,--resume,--continue, and--timeout <value>as runtime controls and do not include them in the task text passed through. - Preserve the user's task text as-is apart from stripping routing flags.
- Return the stdout of the companion command exactly as-is.
- If the Bash call fails because the helper exited non-zero with a recognizable error (auth missing, quota exhausted, model unavailable), surface the helper's stderr verbatim and recommend
/grok:setup. Do not swallow this case silently. - If the Bash call fails for any other reason (helper not found, unrecoverable spawn failure), return nothing.
Response style:
- Do not add commentary before or after the forwarded companion output.
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.
- 8d ago First seen · 44 lines · 88 tokens per session scan A 09bf005b0e72
grok-rescue is an agent published in the GitHub repository LovelaceLoom/grok-plugin-cc (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 88 tokens to every session and 779 once invoked, about $0.0004 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 agents, from other repositories
code-explorer
Read-only codebase explorer — searches, maps, and explains code structure. Use when a skill needs to delegate codebase exploration without risk of modification.
code-locator
Delegated, token-isolated code search for C#/.NET or Unreal C++ projects open in JetBrains Rider. Hand it "where is X defined", "what calls Y", "all usages of Z", "find the file named W", "type info at this position" — it uses Rider's MCP symbol/reference index (not raw grep) and returns ONLY a compact file:line…
explorer-opus
Deeply analyzes complex codebases with comprehensive reasoning to trace subtle execution paths, identify non-obvious root causes, and map intricate architectural dependencies.
log-analyst
Delegated, token-isolated game-engine/build/structured log analysis. Hand it a log path (Unreal Saved/Logs, Unity Editor.log, Godot output, MSVC/UBT/MSBuild build output, or any .log/.jsonl) plus a question — "what errors", "what's flooding it", "what changed since last run", "track this scalar over time", "which…
reqord-explorer
You are an expert code analyst specializing in tracing and understanding feature implementations, with deep knowledge of Reqord's requirements-driven development workflow.
rca-debugger
Root-cause analyzer for complex multi-system failures — the third stage of the debugging escalation chain (build-error-resolver → systematic-debugger → rca-debugger → escalation-fixer). Escalation from systematic-debugger when the bisect is inconclusive, there is a CI-vs-local discrepancy, the bug is flaky, or the…