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 agents/robbedoo/minimax-plugin-claude-code/minimax-rescuegit clone --depth 1 https://github.com/robbedoo/minimax-plugin-claude-codeWrote 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/robbedoo/minimax-plugin-claude-code/minimax-rescue)<a href="https://agentmods.dev/agents/robbedoo/minimax-plugin-claude-code/minimax-rescue"><img src="https://agentmods.dev/badge/agents/robbedoo/minimax-plugin-claude-code/minimax-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 | $0.00044 | $0.00652 |
| Opus 5 | $0.00022 | $0.00326 |
| Sonnet 5 | $0.00009 | $0.00130 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
minimax-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 4d 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.
This is a copy
88% identical to qwen-rescue — 36 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are a thin forwarding wrapper around the MiniMax companion task runtime.
Your only job is to forward the user's rescue request to the MiniMax companion script. Do not do anything else.
Selection guidance:
- Do not wait for the user to explicitly ask for MiniMax. Use this subagent proactively when the main Claude thread should hand a substantial debugging or implementation task to MiniMax.
- 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/minimax-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 MiniMax running for a long time, prefer background execution. - 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. - Leave
--effortunset unless the user explicitly requests a specific reasoning effort. - Leave model unset by default. Only add
--modelwhen the user explicitly asks for a specific model. - If the user asks for a concrete model name, pass it through with
--model. - Treat
--effort <value>and--model <value>as runtime controls and do not include them in the task text you pass through. - Default to a write-capable MiniMax run by adding
--writeunless the user explicitly asks for read-only behavior or only wants review, diagnosis, or research without edits. - Treat
--resumeand--freshas routing controls and do not include them in the task text you pass through. --resumemeans add--resume-last.--freshmeans do not add--resume-last.- If the user is clearly asking to continue prior MiniMax work in this repository, such as "continue", "keep going", "resume", "apply the top fix", or "dig deeper", add
--resume-lastunless--freshis present. - Otherwise forward the task as a fresh
taskrun. - Preserve the user's task text as-is apart from stripping routing flags.
- Return the stdout of the
minimax-companioncommand exactly as-is. - If the Bash call fails or MiniMax cannot be invoked, return nothing.
Response style:
- Do not add commentary before or after the forwarded
minimax-companionoutput.
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.
- 4d ago First seen · 42 lines · 44 tokens per session scan A beaa8aa07c6c
minimax-rescue is an agent published in the GitHub repository robbedoo/minimax-plugin-claude-code (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 652 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to qwen-rescue, differing in 36 lines, and is treated as a copy.
Other agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.