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.
curl -O https://raw.githubusercontent.com/FavioVazquez/mollify/main/.claude/commands/mollify-cleanup.mdgit clone --depth 1 https://github.com/FavioVazquez/mollifyWrote 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/commands/faviovazquez/mollify/mollify-cleanup)<a href="https://agentmods.dev/commands/faviovazquez/mollify/mollify-cleanup"><img src="https://agentmods.dev/badge/commands/faviovazquez/mollify/mollify-cleanup.svg" alt="Measured on agentmods" 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.00020 | $0.00314 |
| Opus 5 | $0.00010 | $0.00157 |
| Sonnet 5 | $0.00004 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
mollify-cleanup 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 8d 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
Mollify report
!mollify audit $ARGUMENTS --format json
Task
Review the audit output above and propose remediation. This is advisory: do NOT edit files without explicit user approval.
- Summarize findings, leading with
confidence: certain; citepath:lineand thefingerprint, grouped byrule. - Identify the findings whose action has
auto_fixable: trueAND whoseconfidenceiscertain— only these are safe to act on. For each, describe the exact edit you would make (the actiondescription), and ask the user to confirm before you apply it. - For everything else (
likely/uncertain, or any deletion), explain the reason/trace and let the user decide. To silence a known-good finding, offer to add itssuppression_commenton the relevant line instead of deleting code. - After any approved edits, re-run
mollify audit --format jsonand confirm the corresponding fingerprints are gone.
mollify fix --apply auto-removes certain unused symbols; for anything else apply changes yourself with the
editor, then re-audit.
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.
- 8d ago First seen · 29 lines · 20 tokens per session scan A aab84cfbf2c2
mollify-cleanup is a command published in the GitHub repository FavioVazquez/mollify (6 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 314 once invoked, about $0.0001 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.
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…
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…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.