/diff
[stable] Compare security posture between two git refs to find new/fixed vulnerabilities and track regression
$ npx -y skills add allsmog/vuln-scout --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/diff
Context preview
What this command does when you run it.
[stable] Compare security posture between two git refs to find new/fixed vulnerabilities and track regression
Command definition
diff.mdname: diff
description: "[stable] Compare security posture between two git refs to find new/fixed vulnerabilities and track regression"
argument-hint: "<base-ref> [<head-ref>] [--tools semgrep] [--format md|json] [--fail-on-regression]"
allowed-tools:
- Bash
- Glob
- Read
- Write
Differential Security Analysis
Compare security findings between two git refs. Shows new vulnerabilities introduced, vulnerabilities fixed, and severity changes.
Usage
/vuln-scout:diff HEAD~5
/vuln-scout:diff v1.0.0 v2.0.0
/vuln-scout:diff main feature/auth --fail-on-regression
Flags
| Flag | Effect | |------|--------| | `base-ref` | Git ref to compare against (required) | | `head-ref` | Git ref to compare (default: HEAD) | | `--tools` | Scanning tools to use (default: semgrep) | | `--format` | Output format: `md` or `json` | | `--fail-on-regression` | Exit 2 if regression score > 0 (more new findings than fixed) |
Workflow
Step 1: Scan baseline
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/run_diff.py" \
--base <base-ref> \
--head <head-ref> \
--tools <tools> \
--project-root .The script handles git checkout, scanning both refs, and computing the diff.
Step 2: Display results
Show the diff report:
- **New findings**: vulnerabilities introduced since the baseline
- **Fixed findings**: vulnerabilities that no longer appear
- **Changed findings**: same location but different severity/verdict
- **Regression score**: positive = worse, negative = better
- **New/removed endpoints**: attack surface changes
Step 3: Exit code
- `0`: no regression (fixed >= new, or `--fail-on-regression` not set)
- `2`: regression detected (with `--fail-on-regression`)
Read more
name: diff description: "[stable] Compare security posture between two git refs to find new/fixed vulnerabilities and track regression" argument-hint: "<base-ref> [<head-ref>] [--tools semgrep] [--format md|json] [--fail-on-regression]" allowed-tools: - Bash - Glob - Read - Write
Differential Security Analysis
Compare security findings between two git refs. Shows new vulnerabilities introduced, vulnerabilities fixed, and severity changes.
Usage
/vuln-scout:diff HEAD~5 /vuln-scout:diff v1.0.0 v2.0.0 /vuln-scout:diff main feature/auth --fail-on-regression
Flags
| Flag | Effect | |------|--------| | `base-ref` | Git ref to compare against (required) | | `head-ref` | Git ref to compare (default: HEAD) | | `--tools` | Scanning tools to use (default: semgrep) | | `--format` | Output format: `md` or `json` | | `--fail-on-regression` | Exit 2 if regression score > 0 (more new findings than fixed) |
Workflow
Step 1: Scan baseline
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/run_diff.py" \
--base <base-ref> \
--head <head-ref> \
--tools <tools> \
--project-root .The script handles git checkout, scanning both refs, and computing the diff.
Step 2: Display results
Show the diff report:
- **New findings**: vulnerabilities introduced since the baseline
- **Fixed findings**: vulnerabilities that no longer appear
- **Changed findings**: same location but different severity/verdict
- **Regression score**: positive = worse, negative = better
- **New/removed endpoints**: attack surface changes
Step 3: Exit code
- `0`: no regression (fixed >= new, or `--fail-on-regression` not set)
- `2`: regression detected (with `--fail-on-regression`)
AI-powered whitebox penetration testing plugin for Claude Code. 9 languages, 22 skills, 7 autonomous agents. STRIDE threat modeling, OWASP 2025 coverage, polyglot monorepo support.
Repo: allsmog/vuln-scout
Other commands on vuln-scout.
- /auto-fix
[experimental] Auto-remediate verified findings by generating patches and optionally creating a PR
Open command - /create-rule
[experimental] Create a custom Semgrep detection rule from a confirmed vulnerability pattern
Open command - /full-audit
[stable] End-to-end security audit with hotspot-aware framework pivots, shared findings.json schema, and CI-friendly workflow flags
Open command - /mobile-audit
[beta] Audit a decompiled Android target — scans jadx_out/sources + apktool_out together and merges findings
Open command - /mutate
[experimental] Security mutation testing -- weaken security controls and check if the scanner detects the resulting vulnerability
Open command - /org-memory-compile
[experimental] Compile human-reviewed scan history into local organization memory
Open command

