agentmods.dev

mollify: Command for Claude Code

.cursor/commands/mollify-dead-code.md

mollify-dead-code is a command for Claude Code, Cursor from FavioVazquez/mollify. It costs 0 tokens per session (319 once invoked), scanned A, original, MIT.

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 Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code command (commands/*.md).

This is FavioVazquez/mollify's own configuration. It tells Claude Code and Cursor how to work on mollify itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mollify configures →

not rated 11repo 7d ago A scan 0 tokens original MIT
View source ↗ FavioVazquez/mollify
Reuse

Borrowing it

Nothing to install: this file belongs to FavioVazquez/mollify. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/FavioVazquez/mollify/main/.cursor/commands/mollify-dead-code.md
Clone the repo
git clone --depth 1 https://github.com/FavioVazquez/mollify

Made for: Claude Code, Cursor.

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

agentmods badge for mollify-dead-code

README.md
[![agentmods](https://agentmods.dev/badge/commands/faviovazquez/mollify/mollify-dead-code/github.svg)](https://agentmods.dev/commands/faviovazquez/mollify/mollify-dead-code)
Your own site
<a href="https://agentmods.dev/commands/faviovazquez/mollify/mollify-dead-code"><img src="https://agentmods.dev/badge/commands/faviovazquez/mollify/mollify-dead-code/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.

agentmods 80×15 button for mollify-dead-code

Your own site · 80×15
<a href="https://agentmods.dev/commands/faviovazquez/mollify/mollify-dead-code"><img src="https://agentmods.dev/badge/commands/faviovazquez/mollify/mollify-dead-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00319
Opus 5.5 $0.00000 $0.00128
Sonnet 5.5 $0.00000 $0.00064
Haiku 4.5 $0.00000 $0.00032

Measured 1mo ago against content hash 00ede29eb6d4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

.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. 1mo 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 (11 stars, last pushed 7d 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

qa-changes

This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…

OpenHands/extensions · 63 tokens

auditar-cascading

Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.

luanpdd/kit-mcp · 54 tokens

react-native

Command "react-native" from getsentry/toolkit, covering xcode build step (react-native xcode) and important notes.

getsentry/toolkit · 0 tokens

http-service

Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.

MadAppGang/magus · 27 tokens

doctor

Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…

doncheli/don-cheli-sdd · 76 tokens

doctor

Badi configuration validation. Checks all Badi components and produces a diagnostic report.

fatihkan/badi · 0 tokens