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/commands/vasihemanth/grok-build-plugin/rescue)<a href="https://agentmods.dev/commands/vasihemanth/grok-build-plugin/rescue"><img src="https://agentmods.dev/badge/commands/vasihemanth/grok-build-plugin/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.00016 | $0.00539 |
| Opus 5 | $0.00008 | $0.00269 |
| Sonnet 5 | $0.00003 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
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 6d 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 it in the foreground. - If neither flag is present, default to foreground for small bounded tasks, background for open-ended ones.
--backgroundand--waitare Claude Code execution flags. Do not forward them as task text.--model,--effort,--read-onlyare runtime controls. Preserve them but do not treat them as task text.- If the request includes
--resume-lastor--fresh, the user already chose; do not ask. - Otherwise, check for a resumable Grok task session for this repo:
node "${CLAUDE_PLUGIN_ROOT}/scripts/grok-companion.mjs" task-resume-candidate --json
- If that reports
available: true, useAskUserQuestionexactly once with these two choices:Continue current Grok sessionStart a new Grok session
- If the user is clearly giving a follow-up ("continue", "keep going", "apply the top fix", "dig deeper"), put
Continue current Grok session (Recommended)first; otherwise putStart a new Grok session (Recommended)first. - If the user chooses continue, add
--resume-lastbefore routing to the subagent. If they choose new, add--fresh. - If
available: false, do not ask. Route normally.
Operating rules:
- The subagent is a thin forwarder. Return its stdout verbatim. Do not paraphrase or add commentary.
- If the companion reports Grok is missing or not logged in, stop and tell the user to run
/grok:setup. - If the user gave no request, ask what Grok should do.
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.
- 6d ago First seen · 38 lines · 16 tokens per session scan A e8f2063edd3d
rescue is a command published in the GitHub repository VasiHemanth/grok-build-plugin (25 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 539 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-30.
Other commands, from other repositories
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
fec-review
Conduct a standardized review of the specified file or recently changed front-end code, output a graded review report and save it as a Markdown file.
fec-doc-sync
Sync README, docs, environment variables, scripts, API/routing/component descriptions and deployment instructions from code and project sources of truth.
fec-smell
Diagnose frontend code smells with evidence and candidate refactorings without changing business code.
project_init
이 프로젝트를 ocul-pm 추적 대상으로 초기화 (.oculpm/ + 기록 규칙 생성) — 사용자가 직접 실행하는 명시적 시작.
viberevert-setup
Enable VibeRevert for this project by installing its MCP server into Cursor.