A read-only report and proposed-refactoring workflow for measuring unnecessary complexity in an existing code repository. It checks dead exports, duplicated code, complexity hotspots, unused dependencies, and possible deletion size before suggesting changes.

Use it to assess repository bloat, write a BLOAT-REPORT.md scorecard, and—when the test suite passes—propose cleanup work as a pull request.

Large or inherited repositories can contain excess code that is difficult to judge by inspection. The scorecard turns that concern into a measured report, while tests act as a safety check before changes are proposed.

debloat — Command by randomittin

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/randomittin/heimdall/debloat

Clone the repo

git clone --depth 1 https://github.com/randomittin/heimdall

Per session 62 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,211 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.

Model	Per session	Once invoked
Fable 5	$0.00062	$0.01211
Opus 5	$0.00031	$0.00606
Sonnet 5	$0.00012	$0.00242
Haiku 4.5	$0.00006	$0.00121

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

Security

Grade A, and why

debloat 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.

commands/debloat.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Debloat — Retroactive Whole-Repo Bloat Removal

Turn the H-2 bloat engine (bin/bloat-gate) on an ENTIRE existing repo. This is the adoption hook: a cold-repo, no-setup command that produces a real bloat scorecard, and — only when it can prove safety — proposes removals as a PR.

When to use

Someone wants a bloat read on a repo Heimdall did not build (the reply-guy reply).
Before adopting the per-wave bloat gate, to clear the existing debt.
To turn "this codebase feels bloated" into a measured, prioritized PR.

Instructions

Always start read-only. Run the one-word scorecard on any repo:
```
bin/heimdall-debloat report [<path>]      # <path> defaults to cwd
```
report is the friendly, screenshot-worthy entrypoint (a back-compatible alias of --report-only). It runs ONLY the read-only scorecard pass, writes BLOAT-REPORT.md (dead exports, duplication clusters, complexity hotspots, unused deps, candidate-deletion LOC estimate), makes NO changes, and prints a truecolor BLOAT SCORECARD card to the terminal. The equivalent legacy form still works and is unchanged:
```
bin/heimdall-debloat --report-only --repo <path>
```
Present the report. Skipped axes mean the analysis tool is absent — say so honestly; an absent tool is a gap, never a pass.

The BLOAT SCORECARD card. report (and --report-only when run interactively on a tty) prints a one-frame scorecard: the 5 axes — dead exports, duplication %, cyclomatic complexity, dependency creep, LOC budget — each with its real value from the bloat-gate run and a ✓ / ⚠ / ✗ glyph, plus an overall verdict (LEAN / NEEDS TRIMMING / BLOATED, or INCONCLUSIVE when every axis was skipped) and the repo name. Numbers come straight from the same data as BLOAT-REPORT.md; an axis whose tool is absent reads skipped: needs <tool> — never a fabricated number. Piped / CI output is clean plain text (zero ANSI), so it is safe to redirect or capture.

Read the full file on GitHub · 97 lines

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.

2d ago First seen · 97 lines · 62 tokens per session scan A 3e87e49a8e84

Subscribe to this mod's changes

debloat is a command published in the GitHub repository randomittin/heimdall (5 stars, last pushed 12d ago), licensed MIT. It adds 62 tokens to every session and 1,211 once invoked, about $0.0003 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-31.

Debugging ai-coding anthropic claude-code claude-plugin cli developer-tools

debloat

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Debloat — Retroactive Whole-Repo Bloat Removal

When to use

Instructions

What this file has done since we first saw it

Other commands, from other repositories

autocode

autocode-new

analyze-repo

doctor

dispatcher

standup