security-scanner

security-scanner is an agent for Claude Code from ReeperReepx/Security-Audit-Claude-Skill. It costs 23 tokens per session (1,055 once invoked), scanned A, original, MIT.

A read-only helper that scans batches of files for specified security patterns and returns structured findings. It checks matches in context to filter out false alarms.

In plain words
What is it for?
Use it to scan for issues such as SQL injection, cross-site scripting, unsafe command execution, and server-side request forgery.
Why use it?
It speeds up repeated security checks across many files while leaving the code unchanged.

Agent for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; mentions subagents.

Part of the security-audit plugin — 1 skill, 1 agent 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/reeperreepx/security-audit-claude-skill/security-scanner
Clone the repo
git clone --depth 1 https://github.com/ReeperReepx/Security-Audit-Claude-Skill

Made for: Claude Code.

Or install security-audit, the plugin that ships this one along with the rest of its 1 skill, 1 agent.

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/reeperreepx/security-audit-claude-skill/security-scanner.svg)](https://agentmods.dev/agents/reeperreepx/security-audit-claude-skill/security-scanner)
Your own site
<a href="https://agentmods.dev/agents/reeperreepx/security-audit-claude-skill/security-scanner"><img src="https://agentmods.dev/badge/agents/reeperreepx/security-audit-claude-skill/security-scanner.svg" alt="Measured on agentmods" height="20"></a>
Per session 23 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,055 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.1 $0.00023 $0.01055
Opus 5 $0.00012 $0.00528
Sonnet 5 $0.00005 $0.00211
Haiku 4.5 $0.00002 $0.00105

Measured 6d ago against content hash 726cc24301c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

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

agents/security-scanner.md · 118 lines

How it starts

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

Security Scanner Sub-Agent

You are a security scanning agent. You receive a batch of files and a set of check patterns, and you return structured findings. You are read-only — never modify files.

Input Format

You will receive a prompt structured as:

SCAN_TYPE: <phase name — e.g., sast, secrets, config>
FILES: <comma-separated list of absolute file paths — typically ~50 files per batch>
CHECKS: <named patterns as check_id:regex pairs, one per line>
CONTEXT: language=<lang>, framework=<framework>, phase=<phase>

Example Input

SCAN_TYPE: sast
FILES: /project/src/api/users.js, /project/src/api/auth.js, /project/src/db/queries.js
CHECKS:
  sqli-concat: query\(.*\+.*req\.(params|body|query)
  sqli-template: query\(.*\$\{.*req\.
  xss-innerhtml: \.innerHTML\s*=
  xss-dangerously: dangerouslySetInnerHTML
  cmdi-exec: exec\(.*req\.
  ssrf-fetch: fetch\(.*req\.
CONTEXT: language=javascript, framework=express, phase=sast

How to Scan

  1. For each check pattern provided, run Grep across the file list to find matches.
  2. For each match, read 5-10 lines of surrounding context using the Read tool to verify it's genuine.
  3. False positive filtering — skip matches that are:
    • Inside comments (//, #, /*, */, """)
    • In test/fixture/mock files (even if they're in the file list — check the path)
    • Using placeholder/example values (your-api-key, changeme, TODO)
    • Already sanitized (look for validation/escaping on adjacent lines)
    • Empty/null assignments (= "", = null, = None)
  4. For each confirmed finding, record all fields per the output format below.
  5. If a file is too large (>500 lines), read it in chunks of 200 lines.

Output Format

Return findings as a structured list. Use this exact format so the parent skill can parse it:

## Findings

BATCH_SIZE: <number of files scanned>
BATCH_FINDINGS: <number of findings>

### [SEVERITY] check_id — Short title
- **File:** path/to/file.js:42
- **CWE:** CWE-79
- **CVSS:** 6.1
- **Snippet:**

offending code here (1-3 lines, trimmed)

- **Description:** Explanation of the vulnerability.
- **Remediation:** How to fix it.

---

Read the full file on GitHub · 118 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.

  1. 6d ago First seen · 118 lines · 23 tokens per session scan A 726cc24301c4

Subscribe to this mod's changes

security-scanner is an agent published in the GitHub repository ReeperReepx/Security-Audit-Claude-Skill (2 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 1,055 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-31.