A command for reviewing and strengthening the security of applications, application programming interfaces, infrastructure, and automation scripts. It uses OWASP guidance, a widely used set of web-security practices, and threat modeling, which means examining how a system could be attacked.

Use it to review code and configurations for injection attacks, authentication and authorization problems, secret exposure, token-handling issues, and other OWASP Top 10 risks.

It helps find common weaknesses before they become security incidents, including unsafe input handling, access-control errors, exposed secrets, and insecure settings.

security — Command by dotclaude

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.

agentmods

npx agentmods add commands/dotclaude/marketplace/security

Clone the repo

git clone --depth 1 https://github.com/dotclaude/marketplace

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 822 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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	$0.00010	$0.00822
Opus 5	$0.00005	$0.00411
Sonnet 5	$0.00002	$0.00164
Haiku 4.5	$0.00001	$0.00082

Measured 2d ago against content hash 1931f9f7236e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

security 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 2d 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.

plugins/backend-security/commands/security.md · 128 lines

How it starts

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

Security Command

Application security with OWASP best practices and threat modeling

Purpose

Comprehensive security review and hardening for applications, APIs, infrastructure, and automation scripts. Identifies vulnerabilities, recommends mitigations, and ensures security best practices are followed.

SECURITY FOCUS AREAS

This command helps you identify and fix security issues across:

Input Validation & Injection Prevention

SQL injection vulnerabilities
Command injection risks
LDAP/XPath/XML injection
Path traversal attacks
Input sanitization gaps

Authentication & Authorization

Broken authentication flows
Session management issues
Weak credential storage
Authorization bypass vulnerabilities
JWT/token handling problems

Secrets Management

Hardcoded credentials detection
API keys in code or configs
Unencrypted sensitive data
Secrets in logs or error messages
Insecure secret transmission

OWASP Top 10 Coverage

Broken Access Control
Cryptographic Failures
Injection Flaws
Insecure Design
Security Misconfiguration
Vulnerable Components
Authentication Failures
Software/Data Integrity Failures
Security Logging Failures
Server-Side Request Forgery

Bash Script Security

Command injection vulnerabilities
Unquoted variable usage
Hardcoded secrets detection
Insufficient input validation
Dangerous command patterns
Permission misconfigurations

Arguments

$1 (Required): Security concern or component to review

Authentication flow, API endpoint, shell script, configuration, etc.

$2 (Optional): Specific focus area

owasp: OWASP Top 10 systematic review
injection: Injection vulnerability focus
auth: Authentication/authorization review
secrets: Secrets management audit
bash: Shell script security review
api: API security assessment

Examples

OWASP Security Review

/security "Review authentication flow" owasp

Systematic OWASP Top 10 review of authentication implementation

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

2d ago First seen · 128 lines · 10 tokens per session scan A 1931f9f7236e

Subscribe to this mod's changes

security is a command published in the GitHub repository dotclaude/marketplace (42 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 822 once invoked, about $0.0001 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-08-30.

Backend and APIs Code review Security

security