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/autopsy)<a href="https://agentmods.dev/agents/rune-kit/rune/autopsy"><img src="https://agentmods.dev/badge/agents/rune-kit/rune/autopsy/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/autopsy"><img src="https://agentmods.dev/badge/agents/rune-kit/rune/autopsy.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.00286 |
| Opus 5.5 | $0.00016 | $0.00114 |
| Sonnet 5.5 | $0.00008 | $0.00057 |
| Haiku 4.5 | $0.00004 | $0.00029 |
Grade A, and why
autopsy 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 autopsy skill — Rune's codebase health analyzer.
Quick Reference
Workflow:
- Structure Scan — via scout: files, LOC, entry points, import graph, tests, configs
- Module Analysis — for each module: LOC, function count, nesting depth, cyclomatic complexity, coverage
- Health Scoring — 6 dimensions: complexity, test coverage, documentation, dependencies, code smells, maintenance = 0-100 per module
- Risk Assessment — git archaeology: hotspots, stale files, dead code, circular deps
- Generate RESCUE-REPORT.md — saved to project root with Mermaid diagram
- Report — summary with health score per tier, ranked modules
Critical Rules:
- MUST scan actual code metrics — not estimate or guess
- MUST produce quantified health scores — not vague assessments
- MUST identify specific modules ranked by tech debt impact
- MUST NOT recommend refactoring everything — prioritize by impact
Read skills/autopsy/SKILL.md for the full specification.
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 · 27 lines · 39 tokens per session scan A dc995b7f2c5a
autopsy 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 286 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.
defensive-programming-remover
Remove try/catch and null-checks that hide errors without serving a real boundary.
bug-fix-verifier
Independent fresh-context verifier for bug-fix PRs produced by /fix-bug. Receives only the Evidence Record, the reproduction path/command, the bug-notes ledger (read-only), and the PR diff — explicitly NOT the planner's reasoning, the plan.md, or the executor's reasoning. Runs FAILTOPASS (repro now passes), PASSTOPASS…
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.
orc-code-fixer
Executor role — applies a defined list of code changes, runs the project's test suite, and reports a diff. Used by /orc:address to execute reviewer-requested fixes, or any context where a list of changes is already decided and just needs to be made cleanly.
insistir-reviewer
Cross-review agent for insistir multi-agent orchestration. Reviews another agent's implementation and sends structured findings to the lead. Read-only — cannot edit or write files. Can run verification commands (tests, typecheck, lint) via whitelisted Bash. Enforces quality without gatekeeping. Do NOT use directly …