autopsy

A codebase health assessment that measures individual modules across complexity, test coverage, documentation, dependencies, code smells, and maintainability.

In plain words
What is it for?
Use it to inspect repository structure, analyze modules, review code history for hotspots and dead code, rank refactoring priorities, and produce a rescue report.
Why use it?
It replaces broad impressions with measured findings and highlights the parts of a codebase with the greatest technical debt and maintenance risk.

Agent

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 agents/rune-kit/rune/autopsy
Clone the repo
git clone --depth 1 https://github.com/Rune-kit/rune
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 286 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.00039 $0.00286
Opus 5 $0.00019 $0.00143
Sonnet 5 $0.00008 $0.00057
Haiku 4.5 $0.00004 $0.00029

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

Security

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

agents/autopsy.md · 27 lines

What it actually says

You are the autopsy skill — Rune's codebase health analyzer.

Quick Reference

Workflow:

  1. Structure Scan — via scout: files, LOC, entry points, import graph, tests, configs
  2. Module Analysis — for each module: LOC, function count, nesting depth, cyclomatic complexity, coverage
  3. Health Scoring — 6 dimensions: complexity, test coverage, documentation, dependencies, code smells, maintenance = 0-100 per module
  4. Risk Assessment — git archaeology: hotspots, stale files, dead code, circular deps
  5. Generate RESCUE-REPORT.md — saved to project root with Mermaid diagram
  6. 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.

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. 2d ago First seen · 27 lines · 39 tokens per session scan A dc995b7f2c5a

Subscribe to this mod's changes

autopsy is an agent published in the GitHub repository Rune-kit/rune (84 stars, last pushed 17d ago), licensed MIT. It adds 39 tokens to every session and 286 once invoked, about $0.0002 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.

Related

Other agents, from other repositories

polymath

Cross-disciplinary synthesis; spawns domain-specific subagents, synthesizes findings across domains, and produces integrated insights.

pjt222/agent-almanac · 25 tokens

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 …

JairoTorregrosa/jaiskills · 76 tokens

insistir-researcher

Research agent for insistir orchestration. Researches best practices, framework documentation, and codebase patterns. Read-only — cannot edit or write files. Do NOT use directly — spawned by insistir skill orchestration.

JairoTorregrosa/jaiskills · 50 tokens

insistir-learnings-researcher

Knowledge search agent for insistir multi-agent orchestration. Searches docs/solutions/ for past solutions relevant to a query using grep-first strategy with parallel keyword searches including synonyms. Read-only — cannot edit, write, or execute commands. Do NOT use directly — spawned by insistir skill orchestration.

JairoTorregrosa/jaiskills · 68 tokens

insistir-worker

Implementation agent for insistir multi-agent orchestration. Implements a task or applies review fixes, commits, reports to lead. Do NOT use directly — spawned by insistir skill orchestration.

JairoTorregrosa/jaiskills · 42 tokens

askit-file-ops

Applies a specified set of file create and edit operations precisely, reading each target first. Use when delegating bounded file mutations - the role that carries out write and edit work an authoring skill has already decided on.

product-on-purpose/agent-skills-toolkit · 50 tokens