security-review

security-review is a command for coding agents from MilindGaharwar/fettle. It costs 19 tokens per session (251 once invoked), scanned A, a copy of fettle-security-review, Apache-2.0.

A command that checks source code for selected security problems using Ruff security rules and Semgrep's OWASP patterns. Static analysis scans code without running it.

In plain words
What is it for?
Use it to review Python, JavaScript, TypeScript, Go, or other supported code, then group findings by severity and explain exploitation risks and fixes.
Why use it?
It can reveal common vulnerabilities and insecure coding patterns before they reach production. It is not a complete security audit, so manual review and other security tools may still be needed.

Command

Part of the fettle plugin — 34 commands, 4 hooks shipped together

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/milindgaharwar/fettle/security-review
Clone the repo
git clone --depth 1 https://github.com/MilindGaharwar/fettle

Or install fettle, the plugin that ships this one along with the rest of its 34 commands, 4 hooks.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/milindgaharwar/fettle/security-review.svg)](https://agentmods.dev/commands/milindgaharwar/fettle/security-review)
Your own site
<a href="https://agentmods.dev/commands/milindgaharwar/fettle/security-review"><img src="https://agentmods.dev/badge/commands/milindgaharwar/fettle/security-review.svg" alt="Measured on agentmods" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 251 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 88% copy Near-identical to another mod 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.00019 $0.00251
Opus 5 $0.00010 $0.00125
Sonnet 5 $0.00004 $0.00050
Haiku 4.5 $0.00002 $0.00025

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

Security

Grade A, and why

security-review 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 5d 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.

Origin

This is a copy

88% identical to fettle-security-review — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

commands/security-review.md · 38 lines

What it actually says

Run a security review on the target path.

Procedure

  1. Determine target. Use $ARGUMENTS if provided, otherwise the current working directory.

  2. Run the scanner:

    python3 -m fettle.security_review --path TARGET
    
  3. Present findings grouped by severity (CRITICAL/HIGH first).

  4. For each finding, explain:

    • What the vulnerability is
    • How it could be exploited
    • The recommended fix
  5. Offer to fix the highest-severity findings automatically.

Scope

  • Python: ruff S-rules (full) + semgrep OWASP
  • TypeScript/JavaScript/Go: semgrep OWASP only
  • Other languages: limited to semgrep generic rules

This is NOT a comprehensive security audit. It runs available static analysis tools. For production security assessments, complement with manual review and dedicated SAST tools.

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. 5d ago First seen · 38 lines · 19 tokens per session scan A ece074691280

Subscribe to this mod's changes

security-review is a command published in the GitHub repository MilindGaharwar/fettle (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 19 tokens to every session and 251 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to fettle-security-review, differing in 9 lines, and is treated as a copy.