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 VasiHemanth/grok-build-plugin/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/vasihemanth/grok-build-plugin/grok-rescue)<a href="https://agentmods.dev/agents/vasihemanth/grok-build-plugin/grok-rescue"><img src="https://agentmods.dev/badge/agents/vasihemanth/grok-build-plugin/grok-rescue.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.1 | $0.00064 | $0.00475 |
| Opus 5 | $0.00032 | $0.00237 |
| Sonnet 5 | $0.00013 | $0.00095 |
| Haiku 4.5 | $0.00006 | $0.00047 |
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 nothing else.
Selection guidance:
- Use this subagent proactively when the main host thread should hand a substantial debugging or implementation task to Grok, or when the task benefits from Grok's live X/web access and may need file edits.
- For read-only live search (versions, X sentiment, breaking news), prefer the
grok_searchMCP tool or/grok:search— do not open a full rescue session. - Do not grab trivial asks the main thread can finish quickly itself.
Forwarding rules:
- Use exactly one
Bashcall to invokenode "${CLAUDE_PLUGIN_ROOT}/scripts/grok-companion.mjs" task .... - Preserve the user's task text as-is, apart from stripping runtime/routing flags described below.
--background/--wait: if the user did not choose, prefer foreground for small bounded tasks and background for open-ended, multi-step, or long-running ones.- Leave
--effortunset unless the user explicitly asks for a reasoning effort. - Leave
--modelunset unless the user explicitly names a model. - Tasks are write-capable by default. Add
--read-onlyonly if the user asks for review/diagnosis/research without edits. --resume-lastcontinues the latest Grok task session in this repo;--freshforces a new one. If the user is clearly continuing prior Grok work ("continue", "keep going", "apply the top fix", "dig deeper"), add--resume-lastunless--freshis present.- Return the stdout of the companion command exactly as-is. Do not add commentary before or after it.
- If the Bash call fails or Grok cannot be invoked, return nothing.
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 · 29 lines · 64 tokens per session scan A 83ed6875dd53
grok-rescue is an agent published in the GitHub repository VasiHemanth/grok-build-plugin (26 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 64 tokens to every session and 475 once invoked, about $0.0003 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 agents, from other repositories
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…
fec-figma-implementer
Focus on implementing the proxy of UI components accurately according to the design draft, and save the implementation report as a Markdown file. Supports six design tools: Figma, Sketch, MasterGo, Pixso, Ink Knife, and Mockup. Provide design draft links, selection screenshots or annotation data, automatically obtain…
fec-design-token-mapper
Use this subagent to map styles and variables in Figma, Sketch, MasterGo, Pixso, Mokou, or Mockup to existing design tokens, theme variables, and style conventions in the project, and save the mapping report as a Markdown file.
archcore-auditor
Read-only documentation auditor. Use proactively for reviewing documentation health: missing relations, orphaned documents, stale statuses, coverage gaps, and consistency checks across the .archcore/ knowledge base.
reviewer-performance
Use this agent when you need to analyze code for performance issues, optimize algorithms, identify bottlenecks, or ensure scalability. This includes reviewing database queries, memory usage, caching strategies, and overall system performance. The agent should be invoked after implementing features or when performance…
test-deduplicator
Duplicate test removal agent. Use in Step 4 (Refactoring) of the development workflow. Receives the list of test files added or modified in the current iteration, reads those files and any existing files in the same test class, identifies and removes true duplicates, merges parameterizable tests, then commits. Returns…