What is security-audit?

A command for reviewing code for common security weaknesses using the OWASP Top 10, a widely used list of web application risks. It can review specified files or, without a scope, recently changed files.

Use it to audit selected files or recent changes for web security problems. It is useful before review or release when checking authorization, cryptography, input handling, and configuration.

It gives a structured way to look for issues such as broken access control, exposed secrets, injection, missing validation, and unsafe configuration. It helps focus security checks on the relevant part of a codebase.

security-audit — Command for Claude Code by CloudAI-X

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/CloudAI-X/opencode-workflow

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/cloudai-x/opencode-workflow/security-audit/github.svg)](https://agentmods.dev/commands/cloudai-x/opencode-workflow/security-audit)

Your own site

<a href="https://agentmods.dev/commands/cloudai-x/opencode-workflow/security-audit"><img src="https://agentmods.dev/badge/commands/cloudai-x/opencode-workflow/security-audit/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/cloudai-x/opencode-workflow/security-audit"><img src="https://agentmods.dev/badge/commands/cloudai-x/opencode-workflow/security-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 856 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.

Model	Per session	Once invoked
Fable 5.1	$0.00010	$0.00856
Opus 5.5	$0.00004	$0.00342
Sonnet 5.5	$0.00002	$0.00171
Haiku 4.5	$0.00001	$0.00086

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

Security

Grade A, and why

security-audit 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 1mo 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.

commands/security-audit.md · 154 lines

How it starts

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

Security Audit Command

Perform a comprehensive security audit of the codebase or specific files, checking for OWASP Top 10 vulnerabilities and common security issues.

Phase 1: Scope Identification

Determine audit scope:

If $ARGUMENTS provided, focus on specified files/directories
If no arguments, audit recently changed files via git diff --name-only HEAD~5
Identify file types and relevant security concerns for each

Phase 2: OWASP Top 10 Analysis

Check for each OWASP Top 10 (2021) vulnerability:

A01: Broken Access Control

Missing authorization checks
IDOR vulnerabilities
Path traversal risks
Privilege escalation possibilities

A02: Cryptographic Failures

Hardcoded secrets or API keys
Weak encryption algorithms
Missing encryption for sensitive data
Insecure random number generation

A03: Injection

SQL injection vectors
Command injection risks
XSS vulnerabilities
Template injection
LDAP/XML injection

A04: Insecure Design

Missing rate limiting
Lack of input validation
Trust boundary violations
Missing security controls

A05: Security Misconfiguration

Debug mode in production
Default credentials
Overly permissive CORS
Missing security headers
Exposed error messages

A06: Vulnerable Components

Check package.json / requirements.txt / go.mod for known vulnerabilities
Outdated dependencies
Deprecated functions

A07: Authentication Failures

Weak password policies
Missing MFA considerations
Session management issues
Credential stuffing vectors

A08: Software and Data Integrity Failures

Missing integrity checks
Insecure deserialization
Unsigned updates or data

A09: Security Logging Failures

Missing audit logs
Sensitive data in logs
Insufficient monitoring

A10: Server-Side Request Forgery (SSRF)

Unvalidated URLs
Internal network access risks
Cloud metadata exposure

Phase 3: Code Pattern Analysis

Search for dangerous patterns:

Patterns to detect:
- eval(), exec(), system() calls with user input
- Unsanitized SQL queries
- innerHTML with user data
- Disabled security features (verify=False, etc.)
- Hardcoded credentials (password=, secret=, api_key=)
- Debug/verbose modes
- TODO/FIXME security comments

Read the full file on GitHub · 154 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.

1mo ago First seen · 154 lines · 10 tokens per session scan A 1c33c3f71290

Subscribe to this mod's changes

security-audit is a command published in the GitHub repository CloudAI-X/opencode-workflow (276 stars, last pushed 9mo ago), licensed MIT. It adds 10 tokens to every session and 856 once invoked, about $0.0000 per session on Opus 5.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-08-30.