vulnerability-scanner

vulnerability-scanner is an agent for Claude Code from jmanhype/claude-code-plugin-marketplace. It costs 0 tokens per session (252 once invoked), scanned A, original, MIT.

A code-security scanning agent that checks for common weaknesses, known CVEs, and exploitable patterns. CVEs are publicly recorded security flaws in software and dependencies.

In plain words
What is it for?
Use it to scan code for SQL, command, and code injection; path traversal; hardcoded credentials; missing access controls; unsafe logs; and outdated or vulnerable dependencies.
Why use it?
It helps find accidental security holes that a backdoor-focused review may miss. It groups findings such as injection risks, weak access controls, exposed data, and vulnerable libraries.

Agent for Claude Code

Part of the code-safety-monitor plugin — 8 commands, 6 agents 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 agents/jmanhype/claude-code-plugin-marketplace/vulnerability-scanner
Clone the repo
git clone --depth 1 https://github.com/jmanhype/claude-code-plugin-marketplace

Made for: Claude Code.

Or install code-safety-monitor, the plugin that ships this one along with the rest of its 8 commands, 6 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.

agentmods badge for vulnerability-scanner

README.md
[![agentmods](https://agentmods.dev/badge/agents/jmanhype/claude-code-plugin-marketplace/vulnerability-scanner.svg)](https://agentmods.dev/agents/jmanhype/claude-code-plugin-marketplace/vulnerability-scanner)
Your own site
<a href="https://agentmods.dev/agents/jmanhype/claude-code-plugin-marketplace/vulnerability-scanner"><img src="https://agentmods.dev/badge/agents/jmanhype/claude-code-plugin-marketplace/vulnerability-scanner.svg" alt="Measured on agentmods" 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 252 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00252
Opus 5 $0.00000 $0.00126
Sonnet 5 $0.00000 $0.00050
Haiku 4.5 $0.00000 $0.00025

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

Security

Grade A, and why

vulnerability-scanner 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.

plugins/code-safety-monitor/.claude/agents/vulnerability-scanner.md · 57 lines

What it actually says

Vulnerability Scanner Agent

You scan code for known security vulnerabilities, CVEs, and common exploit patterns.

Scan Categories

1. Injection Vulnerabilities

  • SQL injection
  • Command injection
  • Code injection
  • Path traversal

2. Authentication & Authorization

  • Hardcoded credentials
  • Weak password policies
  • Missing access controls
  • Session management issues

3. Data Exposure

  • Sensitive data in logs
  • Unencrypted communications
  • Information disclosure

4. Common CVEs

  • Known vulnerable dependencies
  • Outdated library versions
  • Unpatched security flaws

Usage

/scan-code --check-vulnerabilities code.py

Output:

🔍 VULNERABILITY SCAN RESULTS

Critical (2):
- SQL Injection: Line 45, user input not sanitized
- Hardcoded API Key: Line 12, credentials in source

High (1):
- Path Traversal: Line 78, unsanitized file path

Medium (3):
...

Integration

Complements backdoor detection:

  • Backdoor detector: Finds intentional malice
  • Vulnerability scanner: Finds unintentional weaknesses

Both contribute to overall safety score.

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 · 57 lines · 0 tokens per session scan A 66fe6fd553ca

Subscribe to this mod's changes

vulnerability-scanner is an agent published in the GitHub repository jmanhype/claude-code-plugin-marketplace (27 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 252 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-30.