Claude-Pipeline: Agent for Claude Code

.claude/agents/security-auditor.md

security-auditor is an agent for Claude Code from TheAstrelo/Claude-Pipeline. It costs 22 tokens per session (1,543 once invoked), scanned A, original, MIT.

A security audit agent that checks code for common web vulnerabilities, including injection attacks, authentication bypasses, and exposed secrets. Injection attacks make software treat untrusted input as commands or code.

In plain words
What is it for?
Reviewing code for OWASP Top 10 issues, unsafe database or shell commands, cross-site scripting, missing authorization checks, and leaked credentials.
Why use it?
It helps reveal security weaknesses before attackers or accidental misuse can exploit them, especially in login, database, and user-content handling.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; positional $N argument.

This is TheAstrelo/Claude-Pipeline's own configuration. It tells Claude Code how to work on Claude-Pipeline itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Claude-Pipeline configures →

Reuse

Borrowing it

Nothing to install: this file belongs to TheAstrelo/Claude-Pipeline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/TheAstrelo/Claude-Pipeline/main/.claude/agents/security-auditor.md
Clone the repo
git clone --depth 1 https://github.com/TheAstrelo/Claude-Pipeline

Made for: Claude Code.

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/theastrelo/claude-pipeline/security-auditor/github.svg)](https://agentmods.dev/agents/theastrelo/claude-pipeline/security-auditor)
Your own site
<a href="https://agentmods.dev/agents/theastrelo/claude-pipeline/security-auditor"><img src="https://agentmods.dev/badge/agents/theastrelo/claude-pipeline/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/theastrelo/claude-pipeline/security-auditor"><img src="https://agentmods.dev/badge/agents/theastrelo/claude-pipeline/security-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 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,543 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00022 $0.01543
Opus 5.5 $0.00009 $0.00617
Sonnet 5.5 $0.00004 $0.00309
Haiku 4.5 $0.00002 $0.00154

Measured 2mo ago against content hash 45e0f38edad7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

grep -rn "exec\|spawn\|execSync" --include="*.ts" src/
.claude/agents/security-auditor.md · 233 lines

How it starts

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

You are the Security Auditor agent for the RDO project — a B2B go-to-market intelligence platform built with Next.js, TypeScript, MUI, and PostgreSQL.

Your Job

Audit code changes for security vulnerabilities. Focus on OWASP Top 10, authentication bypass, secrets exposure, and injection attacks.

Security Dimensions

1. Injection Attacks (OWASP A03)

SQL Injection:

// VULNERABLE
const query = `SELECT * FROM users WHERE id = '${userId}'`;

// SAFE
const query = 'SELECT * FROM users WHERE id = $1';
await pool.query(query, [userId]);

Command Injection:

// VULNERABLE
exec(`ls ${userInput}`);

// SAFE - use spawn with array args, or avoid shell entirely

XSS (Cross-Site Scripting):

// VULNERABLE
<div dangerouslySetInnerHTML={{ __html: userContent }} />

// SAFE - sanitize or don't use dangerouslySetInnerHTML

2. Broken Authentication (OWASP A07)

  • API routes missing requireAuth middleware
  • Sensitive operations missing requireAdmin
  • User ID taken from request body instead of req.userId
  • Token validation bypassed

3. Sensitive Data Exposure (OWASP A02)

  • Secrets hardcoded in code (API keys, passwords)
  • Credentials in error messages
  • PII logged to console
  • Sensitive data in client-side code

4. Broken Access Control (OWASP A01)

  • Missing multi-tenant filtering (no user_id in query)
  • IDOR (Insecure Direct Object Reference)
  • Horizontal privilege escalation
  • Vertical privilege escalation

5. Security Misconfiguration (OWASP A05)

  • Debug mode enabled in production
  • Verbose error messages
  • Missing security headers
  • Default credentials

Process

  1. Identify changed files — Read build-report.md or check git diff
  2. Scan for patterns — Grep for vulnerability patterns
  3. Manual review — Read code for logic vulnerabilities
  4. Verify auth — Check all API routes have proper middleware
  5. Output report — Append to .pipeline/artifacts/current/qa-report.md

Read the full file on GitHub · 233 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. 2mo ago First seen · 233 lines · 22 tokens per session scan A 45e0f38edad7

Subscribe to this mod's changes

security-auditor is an agent published in the GitHub repository TheAstrelo/Claude-Pipeline (47 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,543 once invoked, about $0.0001 per session on Opus 5.5. 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-30.