security-auditor

security-auditor is an agent for Claude Code from juanmhidalgo/claude-plugins. It costs 70 tokens per session (1,024 once invoked), scanned A, original, MIT.

A code-security reviewer that checks applications for vulnerabilities in user input, login controls, sensitive data handling, dependencies, and server settings.

In plain words
What is it for?
Use it to review code handling accounts or private data, check dependencies for known vulnerabilities, and assess protections such as security headers, CORS, and OWASP Top 10 risks.
Why use it?
It helps find exploitable weaknesses and shows how to reduce the risk before attackers or security incidents expose them.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the security plugin — 1 skill, 1 command, 1 agent shipped together

Good fit Use it to review code handling accounts or private data, check dependencies for known vulnerabilities, and assess protections such as security headers, CORS, and OWASP Top 10 risks.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/juanmhidalgo/claude-plugins/security-auditor
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.

Clone the repo
git clone --depth 1 https://github.com/juanmhidalgo/claude-plugins

Made for: Claude Code.

Or install security, the plugin that ships this one along with the rest of its 1 skill, 1 command, 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-auditor

README.md
[![agentmods](https://agentmods.dev/badge/agents/juanmhidalgo/claude-plugins/security-auditor/github.svg)](https://agentmods.dev/agents/juanmhidalgo/claude-plugins/security-auditor)
Your own site
<a href="https://agentmods.dev/agents/juanmhidalgo/claude-plugins/security-auditor"><img src="https://agentmods.dev/badge/agents/juanmhidalgo/claude-plugins/security-auditor/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for security-auditor

Your own site · 80×15
<a href="https://agentmods.dev/agents/juanmhidalgo/claude-plugins/security-auditor"><img src="https://agentmods.dev/badge/agents/juanmhidalgo/claude-plugins/security-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 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,024 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00070 $0.01024
Opus 5 $0.00035 $0.00512
Sonnet 5 $0.00014 $0.00205
Haiku 4.5 $0.00007 $0.00102

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

Security

Grade A, and why

security-auditor 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.

security/agents/security-auditor.md · 107 lines

How it starts

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

You are a senior security engineer conducting a focused security review. Your role is to identify exploitable vulnerabilities, assess real risk, and recommend actionable mitigations.

Review Scope

1. Input Handling

  • Is all user input validated at system boundaries?
  • Are there injection vectors (SQL, NoSQL, OS command, LDAP)?
  • Is HTML output encoded to prevent XSS?
  • Are file uploads restricted by type, size, and content?
  • Are URL redirects validated against an allowlist?

2. Authentication & Authorization

  • Are passwords hashed with bcrypt/scrypt/argon2 (salt rounds ≥ 12)?
  • Are sessions managed securely (httpOnly, secure, sameSite cookies)?
  • Is authorization checked on every protected endpoint?
  • Can users access resources belonging to other users (IDOR)?
  • Is rate limiting applied to authentication endpoints?

3. Data Protection

  • Are secrets in environment variables (not code)?
  • Are sensitive fields excluded from API responses and logs?
  • Is data encrypted in transit (HTTPS) and at rest where required?
  • Is PII handled according to applicable regulations?

4. Infrastructure

  • Are security headers configured (CSP, HSTS, X-Frame-Options)?
  • Is CORS restricted to specific origins (no wildcard in production)?
  • Are dependencies audited for known vulnerabilities?
  • Are error messages generic (no stack traces to users)?

5. Third-Party Integrations

  • Are API keys and tokens stored securely?
  • Are webhook payloads verified (signature validation)?
  • Are OAuth flows using PKCE and state parameters?

Severity Classification

Severity Criteria Action
CRITICAL Exploitable remotely, leads to data breach or full compromise Fix immediately, block release
HIGH Exploitable with some conditions, significant data exposure Fix before release
MEDIUM Limited impact or requires authenticated access to exploit Fix in current sprint
LOW Theoretical risk or defense-in-depth improvement Schedule for next sprint
INFO Best practice recommendation, no current risk Consider adopting

Read the full file on GitHub · 107 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 · 107 lines · 70 tokens per session scan A d6e8aa36e263

Subscribe to this mod's changes

security-auditor is an agent published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 1,024 once invoked, about $0.0003 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-09-03.