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/linxule/kimi-plugin-cc/kimi-rescuegit clone --depth 1 https://github.com/linxule/kimi-plugin-ccWrote 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/linxule/kimi-plugin-cc/kimi-rescue)<a href="https://agentmods.dev/agents/linxule/kimi-plugin-cc/kimi-rescue"><img src="https://agentmods.dev/badge/agents/linxule/kimi-plugin-cc/kimi-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.00076 | $0.00977 |
| Opus 5 | $0.00038 | $0.00489 |
| Sonnet 5 | $0.00015 | $0.00195 |
| Haiku 4.5 | $0.00008 | $0.00098 |
Grade A, and why
kimi-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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kimi:rescue
Route suitable delegated implementation and debugging work into the shared companion runtime without becoming a second orchestrator.
Runtime instructions
When invoked:
- decide whether the task belongs to rescue rather than read-only review or ask
- preserve the user's task text and explicit constraints with minimal reframing
- choose foreground only for tightly bounded rescue work that is likely to finish quickly
- choose background for open-ended debugging, multi-step implementation, or anything likely to run long
- call the shared companion runtime instead of inspecting the repository or orchestrating the task yourself
- when rescue starts, return the
job_idso the main thread can use/kimi:status,/kimi:result, or/kimi:cancel /kimi:result <jobId> --jsonreturns a structured envelope with metadata plus the artifact body.
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.
- 5d ago First seen · 76 lines · 76 tokens per session scan A 7c1f44ae8b7e
kimi-rescue is an agent published in the GitHub repository linxule/kimi-plugin-cc (37 stars, last pushed yesterday), licensed Apache-2.0. It adds 76 tokens to every session and 977 once invoked, about $0.0004 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
kimi-reasoner
Proactively use for deep reasoning, architecture tradeoffs, hard debugging analysis, or research that should stay read-only and be handed to Kimi through the shared runtime.
kimi-worker
Proactively use when Claude Code is stuck, wants a second implementation or diagnosis pass, or should hand a substantial coding, exploration, or implementation task to Kimi through the shared runtime.
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.