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.
git clone --depth 1 https://github.com/Rune-kit/runeWrote 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/rune-kit/rune/rescue)<a href="https://agentmods.dev/agents/rune-kit/rune/rescue"><img src="https://agentmods.dev/badge/agents/rune-kit/rune/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/rune-kit/rune/rescue"><img src="https://agentmods.dev/badge/agents/rune-kit/rune/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.00039 | $0.00380 |
| Opus 5.5 | $0.00016 | $0.00152 |
| Sonnet 5.5 | $0.00008 | $0.00076 |
| Haiku 4.5 | $0.00004 | $0.00038 |
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 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 the rescue skill — Rune's legacy code modernization orchestrator.
Quick Reference
Multi-Session Workflow:
- RECON (once) — autopsy health assessment, onboard if no CLAUDE.md, dependency audit, build surgery queue
- SAFETY NET (once) — safeguard characterization tests, boundary markers, config freeze, git tag
- SURGERY×N (one module per session) — blast radius check (≤5 files), invoke surgeon, review, test, commit, save state
- CLEANUP (once) — remove @legacy and @bridge markers after ALL surgery complete
- VERIFY (once) — full test suite, autopsy health comparison (baseline → final), git tag
Hard Gates:
- Safety net BEFORE any surgery — commit + tag
rune-rescue-safety-netfirst - ONE module per session — NEVER refactor two coupled modules together
- Blast radius ≤5 files per surgery — if exceeded, split scope
- Characterization tests MUST pass on unmodified code before surgery
- Full test suite pass before marking rescue complete
State Persistence: RESCUE-STATE.md via journal, session-bridge snapshots. /rune rescue status to check progress.
Refactoring Patterns: Strangler Fig (>500 LOC), Branch by Abstraction, Expand-Migrate-Contract, Extract & Simplify.
Read skills/rescue/SKILL.md for the full specification including context-limit handling and module surgery queue.
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 · 31 lines · 39 tokens per session scan A a7a2e5003530
rescue is an agent published in the GitHub repository Rune-kit/rune (86 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 380 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-30.
Other agents, from other repositories
engineer
Senior software engineer specializing in architecture, implementation, debugging, and code review. Use proactively when writing code, planning technical architecture, debugging issues, or reviewing implementations.
support-engineer
Technical product support, issue diagnosis, customer escalations. Debugging, root cause analysis, knowledge base.
git-investigator
Code archaeology expert. Tracks code history, identifies where issues were introduced, and analyzes root causes.
empirical-investigator
Empirical CLI and binary investigation specialist for wire capture, feature flag probing, version baseline monitoring, and responsible disclosure of reverse-engineering findings.
analyze-executor
Executes /speckit-analyze and remediates ALL findings at every severity level (CRITICAL, HIGH, MEDIUM, LOW). After running the analysis, this agent fixes each finding, researching with web search, library docs, codebase exploration, and local file analysis whatever current evidence does not settle, then applies the…
architect
Deep technical work. Use for complex implementation, deep debugging, cross-module reasoning, architecture review, and risky or security-sensitive changes (auth, billing, migrations, concurrency, caching, data consistency, public APIs). Also reviews work from cheaper agents for hidden flaws.