What is mollify-security?

A command that scans a repository with Mollify for possible security problems and groups the results by issue type and confidence. Mollify supplies evidence for review rather than deciding whether an issue is definitely exploitable.

Use it to find candidates such as SQL injection, unsafe evaluation, hardcoded secrets, weak cryptography, disabled TLS checks, and missing request timeouts, then plan remediation after verification.

It gives security findings a stable reference, explanation, and confidence level, making them easier to verify and prioritise. The command is read-only and does not fix files.

How FavioVazquez/mollify configures Claude Code and Cursor

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

README.md

[![agentmods](https://agentmods.dev/badge/commands/faviovazquez/mollify/mollify-security/github.svg)](https://agentmods.dev/commands/faviovazquez/mollify/mollify-security)

Your own site

<a href="https://agentmods.dev/commands/faviovazquez/mollify/mollify-security"><img src="https://agentmods.dev/badge/commands/faviovazquez/mollify/mollify-security/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/faviovazquez/mollify/mollify-security"><img src="https://agentmods.dev/badge/commands/faviovazquez/mollify/mollify-security.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 261 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00261
Opus 5.5	$0.00000	$0.00104
Sonnet 5.5	$0.00000	$0.00052
Haiku 4.5	$0.00000	$0.00026

Measured 1mo ago against content hash 178ed7a697b6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mollify-security 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-security.md · 12 lines

What it actually says

Scan this repository for security candidates with Mollify and summarize the findings. Mollify emits evidence (stable fingerprint, confidence tier, reason), not decisions. You are the verifier.

Steps:

Run mollify security --format json (or call the mollify MCP mollify_security tool). Add --path <dir> if a subproject was specified.
Group findings by rule (dangerous-eval, subprocess-shell-true, sql-injection, unsafe-yaml-load, unsafe-deserialization, tls-verify-disabled, hardcoded-secret, weak-hash, weak-cipher, insecure-random, request-without-timeout, flask-debug-true, jinja2-autoescape-false, try-except-pass) and by confidence, with counts.
List each finding with its file:line, its reason, and the fingerprint.
Do NOT modify files. Present a remediation plan ordered by severity and ask for approval first.

Notes:

These are candidates, not confirmed vulnerabilities — verify each in context.
Act automatically only on confidence: certain; surface likely / uncertain and let the user decide.

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.

1mo ago First seen · 12 lines · 0 tokens per session scan A 178ed7a697b6

Subscribe to this mod's changes

mollify-security 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 261 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.

Security

mollify: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

converge

implement

speckit.bug.fix