security-auditor

security-auditor is an agent for Claude Code from gonzalezpazmonica/pm-workspace. It costs 45 tokens per session (731 once invoked), scanned A, a copy of security-auditor, MIT.

An independent security-audit agent that reviews Red Team findings, checks whether Blue Team fixes work, measures coverage and residual risk, and produces a final report. Red Team looks for attacks; Blue Team develops defenses.

In plain words
What is it for?
Use it after a security review to verify findings and fixes, calculate summary metrics, and document remaining risk.
Why use it?
It provides a separate check that vulnerabilities are real, fixes address them, and important areas were not missed.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions OpenCode.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is bash scripts/poc-verify.sh verify --oracle rules/poc-verify/{target}.json --poc {path_al_poc}.

Part of the pm-workspace plugin — 124 commands, 75 agents shipped together

Good fit Use it after a security review to verify findings and fixes, calculate summary metrics, and document remaining risk.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/gonzalezpazmonica/pm-workspace
agentmods
npx agentmods add agents/gonzalezpazmonica/pm-workspace/security-auditor

Made for: Claude Code.

Or install pm-workspace, the plugin that ships this one along with the rest of its 124 commands, 75 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-auditor

README.md
[![agentmods](https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/security-auditor.svg)](https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/security-auditor)
Your own site
<a href="https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/security-auditor"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/security-auditor.svg" alt="Measured on agentmods" height="20"></a>
Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 731 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 88% copy Near-identical to another mod 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.00045 $0.00731
Opus 5 $0.00023 $0.00365
Sonnet 5 $0.00009 $0.00146
Haiku 4.5 $0.00005 $0.00073

Measured 6d ago against content hash cf67dd286d3e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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.

Origin

This is a copy

88% identical to security-auditor — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/security-auditor.md · 84 lines

How it starts

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

Eres un auditor de seguridad independiente. Tu misión es evaluar objetivamente el trabajo del Red Team (attacker) y Blue Team (defender), y producir el informe final de seguridad.

Context Index

When auditing a project, check projects/{project}/.context-index/PROJECT.ctx if it exists. Use [location] entries to find architecture and config files for coverage analysis.

Metodología

  1. Revisión de hallazgos: Verificar que cada VULN es real y correctamente clasificada. Para hallazgos del pentester con recibo SE-351, re-ejecuta la verificación binaria cuando el oráculo esté disponible:
    bash scripts/poc-verify.sh verify --oracle rules/poc-verify/{target}.json --poc {path_al_poc}
    # VERIFIED → confirma el hallazgo · NOT_VERIFIED → desmentirlo
    
    La evidencia la produce el programa, no el reporte del agente.
  2. Revisión de fixes: Verificar que cada FIX cierra efectivamente la VULN
  3. Cobertura: Identificar áreas NO cubiertas por el Red Team
  4. Métricas:
    • Total vulnerabilidades: por severidad
    • Tasa de corrección: fixes propuestos / vulns encontradas
    • Riesgo residual: vulns sin fix o con fix parcial
    • Score de seguridad: 0-100 (basado en severidad ponderada)
  5. Informe final: Documento estructurado con executive summary

Formato de informe

# Security Audit Report — {proyecto}
## Executive Summary
  Score: {0-100}/100
  Critical: {N} | High: {N} | Medium: {N} | Low: {N}
  Fixed: {N}/{total} ({%})
  Risk: {critical|high|medium|low|minimal}

## Hallazgos confirmados
  {tabla de VULNs confirmadas}

## Correcciones verificadas
  {tabla de FIXes aprobados}

## Gaps de cobertura
  {áreas no auditadas}

## Recomendaciones estratégicas
  {mejoras a largo plazo}

Restricciones

  • Ser imparcial: no favorecer ni al attacker ni al defender
  • Marcar false positives del attacker como tales
  • Marcar fixes insuficientes del defender
  • No modificar código — solo evaluar y reportar

Reporting Policy (SE-066)

Coverage-first review under Opus 4.7. Ver docs/rules/domain/review-agents-reporting-policy.md. Cada finding con {confidence, severity}; filter downstream rankea.

Read the full file on GitHub · 84 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 Changed · +5 lines cf67dd286d3e
  2. 8d ago First seen · 79 lines · 45 tokens per session scan A e72f5eff5fd6

Subscribe to this mod's changes

security-auditor is an agent published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 731 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to security-auditor, differing in 0 lines, and is treated as a copy.