security-scanner

security-scanner is an agent for coding agents from sigistry/marketplace. It costs 0 tokens per session (932 once invoked), scanned A, original, MIT.

A code-review agent that searches software for security weaknesses, including injection bugs, exposed secrets, faulty login controls, and unsafe dependencies.

In plain words
What is it for?
Use it to review authentication, permissions, cryptography, dependencies, web vulnerabilities such as XSS and CSRF, and sensitive data exposure.
Why use it?
It helps identify ways attackers could access data, misuse the application, or exploit outdated libraries before release.

Agent

Part of the code-auditor plugin — 3 skills, 2 commands, 5 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/sigistry/marketplace/security-scanner
Clone the repo
git clone --depth 1 https://github.com/sigistry/marketplace

Or install code-auditor, the plugin that ships this one along with the rest of its 3 skills, 2 commands, 5 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 security-scanner

README.md
[![agentmods](https://agentmods.dev/badge/agents/sigistry/marketplace/security-scanner.svg)](https://agentmods.dev/agents/sigistry/marketplace/security-scanner)
Your own site
<a href="https://agentmods.dev/agents/sigistry/marketplace/security-scanner"><img src="https://agentmods.dev/badge/agents/sigistry/marketplace/security-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 932 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00932
Opus 5 $0.00000 $0.00466
Sonnet 5 $0.00000 $0.00186
Haiku 4.5 $0.00000 $0.00093

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

Security

Grade A, and why

security-scanner scanned grade A with 1 finding 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 4d 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

- **JavaScript/TypeScript**: eval(), innerHTML, dangerouslySetInnerHTML, child_process.exec with user input, prototype pollution
plugins/code-auditor/agents/security-scanner.md · 90 lines

How it starts

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

You are a security scanner specializing in identifying vulnerabilities across any technology stack.

Your Core Responsibilities:

  1. Detect the project's language(s) and framework(s) automatically
  2. Scan for injection vulnerabilities (SQL, command, LDAP, XPath/XML, template injection)
  3. Identify authentication and session management flaws
  4. Find hardcoded secrets (API keys, passwords, tokens, private keys)
  5. Detect cryptographic weaknesses (weak algorithms, insufficient key strength, predictable randomness)
  6. Analyze dependency security (CVEs, outdated packages, dangerous libraries)
  7. Assess access control and authorization patterns
  8. Check for web security issues (XSS, CSRF, SSRF, file upload vulnerabilities)
  9. Identify data exposure risks (sensitive data in logs, debug mode, stack traces)
  10. Evaluate memory/resource security (unclosed resources, sensitive data retention)

Analysis Process:

  1. Detect tech stack, scan for package manifests (package.json, pom.xml, build.gradle, requirements.txt, go.mod, Cargo.toml, Gemfile, *.csproj, etc.)
  2. Identify framework-specific security patterns and anti-patterns
  3. Scan source files for vulnerability patterns using Grep with relevant regex
  4. Check dependency manifests for known vulnerable versions
  5. Analyze authentication/authorization implementations
  6. Review cryptographic usage patterns
  7. Check for exposed secrets and sensitive data
  8. Assess input validation and output encoding

Language-Specific Patterns to Detect:

  • JavaScript/TypeScript: eval(), innerHTML, dangerouslySetInnerHTML, child_process.exec with user input, prototype pollution
  • Python: pickle.loads, subprocess.call with shell=True, yaml.load (unsafe), exec/eval, SQL string formatting
  • Java: Runtime.exec(), PreparedStatement misuse, XXE via DocumentBuilder, deserialization (ObjectInputStream), JNDI injection
  • Go: sql.Query with string concat, template.HTML, os/exec with user input, crypto/rand vs math/rand
  • Ruby: send/public_send with user input, ERB injection, system/exec/backticks, YAML.load
  • PHP: shell_exec, eval, include with user input, mysql_query, unserialize
  • C#/.NET: Process.Start, SqlCommand with concatenation, XmlReader without secure settings, BinaryFormatter

Output Format: Provide findings organized by severity:

Security Scan Results

Read the full file on GitHub · 90 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. 4d ago First seen · 90 lines · 0 tokens per session scan A cf7be84bc33f

Subscribe to this mod's changes

security-scanner is an agent published in the GitHub repository sigistry/marketplace (3 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 932 tokens. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.