security-audit

A security review command that examines an application for common vulnerabilities, including issues from the OWASP Top 10, a widely used list of web security risks.

In plain words
What is it for?
Use it for an interactive application security audit after checking the project's security configuration.
Why use it?
It helps find insecure coding patterns and weaknesses before attackers can exploit them.

Skill for Claude CodeCodex

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 skills/charlesjones-dev/claude-code-plugins-dev/security-audit
Any agent
npx skills add charlesjones-dev/claude-code-plugins-dev --skill security-audit
Clone the repo
git clone --depth 1 https://github.com/charlesjones-dev/claude-code-plugins-dev

Made for: Claude Code, Codex.

Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,749 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 3 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.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.05749
Opus 5 $0.00013 $0.02874
Sonnet 5 $0.00005 $0.01150
Haiku 4.5 $0.00003 $0.00575

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

Security

Grade B, and why

security-audit scanned grade B with 3 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.

Cloud metadata endpointmediumServer-side request forgery

One request to 169.254.169.254 can return temporary IAM credentials.

- SSRF via user-controlled URLs, especially cloud metadata endpoints (169.254.169.254)

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

response = requests.get(user_provided_url)

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

- Command injection via `os.system()`, `subprocess.call(shell=True)`, and `eval()`
plugins/ai-security/skills/security-audit/SKILL.md · 686 lines

How it starts

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

Security Audit

You are a comprehensive security auditor with deep expertise in application security, OWASP Top 10 vulnerabilities, secure coding practices, and defensive security strategies.

Instructions

CRITICAL: This command MUST NOT accept any arguments. If the user provided any text, URLs, or paths after this command (e.g., /security-audit https://example.com or /security-audit ./src), you MUST COMPLETELY IGNORE them. Do NOT use any URLs, paths, or other arguments that appear in the user's message. You MUST ONLY proceed with the interactive workflow as specified below.

BEFORE DOING ANYTHING ELSE: Check the security configuration and then invoke the security auditor subagent as specified in this command. DO NOT skip these steps even if the user provided arguments after the command.

Pre-Audit Check: Security Configuration

Before performing the security audit, check if .claude/settings.json exists and has proper file denial configurations using the Read tool (NOT bash test commands):

  1. Try to read .claude/settings.json using the Read tool
  2. If the file exists and Read succeeds:
    • Parse the JSON content
    • Verify it has a permissions.deny section
    • Count the number of rules in the permissions.deny array
  3. If the file doesn't exist (Read returns error), proceed with warning about missing configuration

IMPORTANT: Use Read tool only - DO NOT use bash test commands as they trigger permission prompts

If less than 4 deny rules are configured:

Display the following warning:

Security Configuration Warning

Your .claude/settings.json file has fewer than 4 file denial rules configured.

For a comprehensive security audit, it's recommended to configure proper file
denial patterns to prevent Claude Code from accidentally reading sensitive files
like credentials, secrets, and environment variables.

Recommendation: Run /security-init first to automatically configure file denial
patterns based on your project's technology stack.

Important: After running /security-init, you must restart Claude Code for
the settings to take effect before running this security audit.

Would you like to:
1. Continue with audit anyway (not recommended)
2. Run /security-init first (recommended - requires restart after)

Read the full file on GitHub · 686 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. 2d ago First seen · 686 lines · 25 tokens per session scan B 92ff7a370693

Subscribe to this mod's changes

security-audit is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (34 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 5,749 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 3 findings (cloud metadata endpoint, makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

gwm

Manage git worktrees across any repository with the gwm Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (gwm exec) or reclaim build artifacts (gwm clean), materialise a PR into a worktree (gwm review), drive a…

kbrdn1/gwm-cli · 379 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens