rescue

A repository command that asks Kimi, an AI coding assistant, to diagnose and modify the current codebase. It can run in the background and continue earlier sessions.

In plain words
What is it for?
Use it to fix a problem across a repository, run longer repair tasks, or resume an earlier rescue session.
Why use it?
It helps with multi-step repair work that may involve applying changes, running tests, and checking the result without manually coordinating each step.

Command

Part of the kimi plugin — 12 skills, 11 commands, 7 agents, 1 hook shipped together

Install

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.

agentmods
npx agentmods add commands/linxule/kimi-plugin-cc/rescue
Clone the repo
git clone --depth 1 https://github.com/linxule/kimi-plugin-cc

Or install kimi, the plugin that ships this one along with the rest of its 12 skills, 11 commands, 7 agents, 1 hook.

Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 271 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.00271
Opus 5 $0.00010 $0.00135
Sonnet 5 $0.00004 $0.00054
Haiku 4.5 $0.00002 $0.00027

Measured 3d ago against content hash 7708b9d2a48a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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.

commands/rescue.md · 23 lines

What it actually says

Run the companion with any user-supplied flags appended after task rescue:

${CLAUDE_PLUGIN_ROOT}/scripts/companion.sh task rescue <args>

Supported flags:

  • --background — spawn as a detached background job and return {job_id} immediately
  • --wait — combined with --background, block until terminal state and return the rendered result
  • -r — resume the latest rescue session for the current repo; any trailing text becomes the next prompt
  • --resume <job-id-or-session-id> — resume a specific prior rescue session without a new prompt payload
  • --fresh — force a new rescue session id instead of reusing a prior session
  • -m, --model <name>

Kimi's extended reasoning is always on for rescue. Budget is 30 min for multi-step apply/test/verify loops; use --background for sessions that need to run longer.

Return the companion stdout verbatim.

Changes

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.

  1. 3d ago First seen · 23 lines · 20 tokens per session scan A 7708b9d2a48a

Subscribe to this mod's changes

rescue is a command published in the GitHub repository linxule/kimi-plugin-cc (37 stars, last pushed 4d ago), licensed Apache-2.0. It adds 20 tokens to every session and 271 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.