agentmods.dev

mollify-dead-code

A repository check for code that appears unused or unreachable, such as unused files, imports, exports, methods, or attributes.

In plain words
What is it for?
Use it to inspect dead-code findings, preview possible deletions, and plan cleanup without changing files automatically.
Why use it?
It helps identify code that may be safe to remove while showing confidence and reasons so dynamic behavior can be reviewed.

Command for Cursor

6 1mo ago A scan 0 tokens original MIT
View the source file FavioVazquez/mollify
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/faviovazquez/mollify/mollify-dead-code
Clone the repo
git clone --depth 1 https://github.com/FavioVazquez/mollify

Made for: Cursor.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 319 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.00000 $0.00319
Opus 5 $0.00000 $0.00160
Sonnet 5 $0.00000 $0.00064
Haiku 4.5 $0.00000 $0.00032

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

Security

Grade A, and why

mollify-dead-code 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 3d 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.

.cursor/commands/mollify-dead-code.md · 12 lines

What it actually says

Find dead code in this repository with Mollify and summarize the findings. Mollify is a deterministic candidate-producer: it emits evidence (each finding has a stable fingerprint, a confidence tier, and a reason), not decisions. You are the verifier.

Steps:

  1. Run mollify dead-code --format json (alias mollify check; or call the mollify MCP mollify_dead_code tool). Add --path <dir> if a subproject was specified.
  2. Group findings by rule (unused-file, unused-export, unused-import, unused-method, unused-attribute, unused-enum-member, unreachable-code, duplicate-export, commented-code) and by confidence (certain / likely / uncertain), with counts.
  3. List every certain finding with its file:line, its reason, the fingerprint, and whether the action's auto_fixable is true.
  4. Do NOT apply any changes. Present a plan and ask for approval first; preview any proposed deletion (file, line, reason) before the user confirms.

Notes:

  • Reachability is static; dynamic imports (getattr/importlib) downgrade confidence to uncertain — treat those as review-only.
  • mollify fix --apply auto-removes certain + auto_fixable unused symbols and imports. To silence a known-good finding, suggest its suppression_comment instead of deleting code.
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. 3d ago First seen · 12 lines · 0 tokens per session scan A 00ede29eb6d4

Subscribe to this mod's changes

mollify-dead-code is a command published in the GitHub repository FavioVazquez/mollify (6 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 319 tokens. 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
Related

Other commands, from other repositories

git

Git operations with intelligent commit messages and workflow optimization.

SuperClaude-Org/SuperClaude_Framework · 11 tokens

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens