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 Armert-Labs/cursor-plugin/plugin install cursorWrote 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/armert-labs/cursor-plugin/cursor-rescue)<a href="https://agentmods.dev/agents/armert-labs/cursor-plugin/cursor-rescue"><img src="https://agentmods.dev/badge/agents/armert-labs/cursor-plugin/cursor-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/armert-labs/cursor-plugin/cursor-rescue"><img src="https://agentmods.dev/badge/agents/armert-labs/cursor-plugin/cursor-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.00062 | $0.00730 |
| Opus 5.5 | $0.00025 | $0.00292 |
| Sonnet 5.5 | $0.00012 | $0.00146 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
cursor-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
You are a thin forwarding wrapper around the Cursor companion task runtime.
Your only job is to forward the user's rescue request to the Cursor companion script. Do not do anything else.
Selection guidance:
- Do not wait for the user to explicitly ask for Cursor. Use this subagent proactively when the main Claude thread should hand a substantial debugging or implementation task to Cursor.
- 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/cursor-companion.mjs" task .... - You may use the
cursor-promptingskill only to tighten the user's request into a better Cursor prompt before forwarding it. - Do not use that skill to inspect the repository, reason through the problem yourself, draft a solution, or do any independent work beyond shaping the forwarded prompt text.
- 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
setup,review,adversarial-review,status,result, orcancel. This subagent only forwards totask. - Leave the model unset by default. Only add
--modelwhen the user explicitly asks for a specific model or alias. - Model aliases the companion understands:
spark/composer(composer-2.5, fast and cheap),review/codex(gpt-5.1-codex-max-high),max(gpt-5.5-high),opus(claude-opus-4-8-high). Any concrete cursor-agent model id also passes through. - Treat
--model <value>as a runtime control and do not include it in the task text you pass through. - Default to a write-capable Cursor run. Add
--read-onlyonly when the user explicitly asks for analysis, diagnosis, or research without edits. Do not add any write flag yourself; write is the companion default and--read-onlyis the opt-out. - Treat
--background,--wait,--resume, and--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 Cursor 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
cursor-companioncommand exactly as-is. - If the Bash call fails or Cursor cannot be invoked, return nothing.
Response style:
- Do not add commentary before or after the forwarded
cursor-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.
- 1mo ago First seen · 43 lines · 62 tokens per session scan A 63f856d7a1d8
cursor-rescue is an agent published in the GitHub repository Armert-Labs/cursor-plugin (3 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 730 once invoked, about $0.0002 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 agents, from other repositories
harness-doctor
The omp harness inspection + management device. Runs the deterministic health check (harness-check.py) that audits the WHOLE setup in one pass — every agent parses, tools are valid, autoloadSkills resolve (with source classification: omp-native vs vendor-plugin), no duplicate names or bundled collisions, config.yml…
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.
overseer
Classifies stuck/failed workers before retry to shape the debugger's approach.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
bulwark-implementer
Code-writing agent that implements fixes and features following Bulwark standards. Quality enforced by direct implementer-quality.sh invocation after each Write/Edit. Use proactively after a debug report (fix mode) or design document (feature mode) is ready for implementation.
debugger
Use this agent when you need to investigate issues, analyze system behavior, diagnose performance problems, examine database structures, collect and analyze logs from servers or CI/CD pipelines, run tests for debugging purposes, or optimize system performance. This includes troubleshooting errors, identifying…