A vulnerability-checking command that investigates whether a reported security issue is genuine, a false alarm, or still needs proof. It supports several programming languages and can reuse cached code-analysis data.

Use it to check one finding, verify all critical findings, or review results from a saved findings file, including issues in JavaScript, TypeScript, Python, Go, Java, PHP, Ruby, C#, and Solidity.

Initial scans often produce leads rather than confirmed problems. Verification helps decide which reports need fixing and which can be closed or investigated further.

verify — Command for Claude Code by allsmog

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add allsmog/vuln-scout

Claude Code

/plugin install vuln-scout

Made for: Claude Code.

Or install vuln-scout, the plugin that ships this one along with the rest of its 32 skills, 15 commands, 9 agents.

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/allsmog/vuln-scout/verify.svg)](https://agentmods.dev/commands/allsmog/vuln-scout/verify)

Your own site

<a href="https://agentmods.dev/commands/allsmog/vuln-scout/verify"><img src="https://agentmods.dev/badge/commands/allsmog/vuln-scout/verify.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 1,572 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.00019	$0.01572
Opus 5	$0.00010	$0.00786
Sonnet 5	$0.00004	$0.00314
Haiku 4.5	$0.00002	$0.00157

Measured 7d ago against content hash c87481264171, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

verify 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 7d 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.

vuln-scout/commands/verify.md · 211 lines

How it starts

The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Verification Workflow

Verify whether a reported item is a real vulnerability, a false positive, or still unresolved.

Philosophy

Pattern matches and sink heuristics produce leads. Verification decides whether those leads stay hotspot, become finding, or close as false_positive.

Modes

Single target

/vuln-scout:verify routes/login.ts:34 --type sql-injection

Batch verify critical findings

/vuln-scout:verify --all-critical

Verify from prior results

/vuln-scout:verify --from .claude/findings.json

Language support

First-party Joern verification is implemented for:

JavaScript / TypeScript
Python
Go
Java
PHP
Ruby
C# when the local Joern frontend is available

Solidity verification is Slither-owned. Joern should return verdict: na_cpg for Solidity findings instead of trying to build a Solidity CPG.

If the target language is not supported for the requested verifier:

return verdict: na_cpg
do not convert that into false_positive

Step 1: Load or create the CPG cache

Cache CPGs by target hash plus language so repeated verification does not restart from scratch.

TARGET_HASH=$(git ls-files -z . | xargs -0 shasum | shasum | awk '{print $1}')
LANGUAGE=<detected-language>
CPG_FILE=".joern/${TARGET_HASH}-${LANGUAGE}.cpg"

if [ ! -f "$CPG_FILE" ] || [ "$NO_CACHE" = "true" ]; then
  mkdir -p .joern
  joern-parse . --output "$CPG_FILE"
fi

Step 2: Choose verifier

Type	Script
`sql-injection`	`verify-sqli.sc`
`command-injection`	`verify-cmdi.sc`
`xss`	`verify-xss.sc`
`path-traversal`	`verify-path.sc`
`ssrf`	`verify-ssrf.sc`
other / mixed	`verify-generic.sc`

Step 3: Run Joern

Single verification:

joern --script "${CLAUDE_PLUGIN_ROOT}/scripts/joern/verify-${VULN_TYPE}.sc" \
  --params cpgFile="$CPG_FILE",file="$FILE",line="$LINE"

Batch verification:

joern --script "${CLAUDE_PLUGIN_ROOT}/scripts/joern/batch-verify.sc" \
  --params cpgFile="$CPG_FILE",findingsFile=".claude/findings.json"

Read the full file on GitHub · 211 lines

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.

7d ago First seen · 211 lines · 19 tokens per session scan A c87481264171

Subscribe to this mod's changes

verify is a command published in the GitHub repository allsmog/vuln-scout (24 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 1,572 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-30.

Claude Code Debugging Security appsec claude-code-plugin sast semgrep threat-modeling

verify