Claude-Pipeline: Command for Claude Code

.claude/commands/security-review.md

security-review is a command for Claude Code from TheAstrelo/Claude-Pipeline. It costs 0 tokens per session (552 once invoked), scanned A, original, MIT.

A command for auditing code changes for common security problems. It checks for injection attacks, authentication bypasses, access-control errors, exposed secrets, and insecure configuration using OWASP-style checks.

In plain words
What is it for?
Use it to review changed files, verify API authentication and user scoping, scan for secrets, and append findings to qa-report.md.
Why use it?
It helps identify vulnerabilities such as SQL injection, cross-site scripting, command injection, broken tenant isolation, and missing authentication checks before release.

Command for Claude Code

Written for Claude Code: installed under .claude/.

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/commands/security-review.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-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/theastrelo/claude-pipeline/security-review/github.svg)](https://agentmods.dev/commands/theastrelo/claude-pipeline/security-review)
Your own site
<a href="https://agentmods.dev/commands/theastrelo/claude-pipeline/security-review"><img src="https://agentmods.dev/badge/commands/theastrelo/claude-pipeline/security-review/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-review

Your own site · 80×15
<a href="https://agentmods.dev/commands/theastrelo/claude-pipeline/security-review"><img src="https://agentmods.dev/badge/commands/theastrelo/claude-pipeline/security-review.svg" alt="Reviewed on agentmods" width="80" 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 552 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.00000 $0.00552
Opus 5 $0.00000 $0.00276
Sonnet 5 $0.00000 $0.00110
Haiku 4.5 $0.00000 $0.00055

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

Security

Grade A, and why

security-review 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 10d 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.

.claude/commands/security-review.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.

Security audit - check for OWASP vulnerabilities, auth bypass, and secrets exposure.


Purpose

Audit code changes for security vulnerabilities:

  • Injection attacks (SQL, XSS, command)
  • Authentication bypass
  • Access control issues
  • Secrets exposure
  • Security misconfiguration

Execution

Use the security-auditor agent.

Input: Read build-report.md to identify changed files.

Process:

  1. Scan for injection patterns:

    • SQL injection: string interpolation in queries
    • XSS: dangerouslySetInnerHTML usage
    • Command injection: exec/spawn with user input
  2. Audit authentication:

    • All API routes have requireAuth/requireAdmin
    • User ID from req.userId, not req.body
  3. Verify access control:

    • Multi-tenant filtering (user_id in queries)
    • No IDOR vulnerabilities
  4. Check for secrets:

    • No hardcoded API keys/passwords
    • No credentials in error messages
  5. Append results to qa-report.md


Vulnerability Patterns

Pattern Risk Detection
${userId} in SQL SQL Injection HIGH
dangerouslySetInnerHTML XSS MEDIUM
exec(userInput) Command Injection CRITICAL
Missing requireAuth Auth Bypass HIGH
Missing user_id filter Data Leak HIGH
Hardcoded secrets Secret Exposure CRITICAL

Output

After audit, report:

## Security Audit Complete

**Verdict:** [PASS | FAIL | CRITICAL]

### Vulnerability Scan
- SQL Injection: [CLEAR | FOUND]
- XSS: [CLEAR | FOUND]
- Command Injection: [CLEAR | FOUND]

### Authentication
- Routes checked: [N]
- Protected: [N]
- Unprotected: [List]

### Access Control
- Multi-tenant filters: [OK | MISSING]
- IDOR risks: [NONE | FOUND]

### Secrets
- Hardcoded secrets: [NONE | FOUND]

### Required Fixes
[If FAIL/CRITICAL, specific fixes with code examples]

### Summary
This concludes the QA pipeline.

Verdict Levels

  • PASS: No vulnerabilities found
  • FAIL: Vulnerabilities found, must fix
  • CRITICAL: Severe vulnerabilities, stop immediately

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. 10d ago First seen · 107 lines · 0 tokens per session scan A 245458aef6c2

Subscribe to this mod's changes

security-review is a command published in the GitHub repository TheAstrelo/Claude-Pipeline (45 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 552 tokens. 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-30.