Skip to main content
skill CX Codex

security-auditor · zhaono1 — Claude Code skill: OWASP security audit

A skill that hunts vulnerabilities in your code: walks the OWASP Top 10, checks configs, dependencies and leaked secrets. Useful before a release or a review.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add zhaono1/agent-playbook --skill security-auditor -a claude-code
Open on GitHub

What security-auditor does

The skill activates when you ask for a security audit or mention vulnerabilities and OWASP. It then works through the ten OWASP Top 10:2025 categories, from broken access control and SSRF to mishandled exceptional conditions and fail-open behaviour. The author is explicit that this list is an awareness taxonomy, not proof of full coverage; for verifiable controls, findings should map to OWASP ASVS or your project's required standard.

Inside there is a checklist across three areas: code (hardcoded secrets, input validation, parameterized queries, auth on protected routes), configuration (debug flags, HTTPS, CORS, security headers, database exposure) and dependencies. Two scripts ship with it: python3 scripts/security_audit.py --name <service-name> --output security-audit.md for the audit run and python3 scripts/find_secrets.py . for secret scanning. The skill is allowed Read, Grep, Glob, Bash and WebSearch, so it reads files and runs commands instead of just talking.

Python 3 has to be present in your environment, since both scripts are invoked through python3. And the skill only earns its keep if you give it access to source and config files — without those, the review collapses into generic advice.

What it helps with

  • find hardcoded secrets and keys in a repo
  • check authorization on sensitive routes and tenant boundaries
  • review config for debug flags, CORS and security headers
  • assess dependency and build supply chain risk
  • test timeout, partial failure and fail-open handling

Example prompts for the agent

  • run a security audit of this service against the OWASP Top 10
  • find vulnerabilities under src/api and list them by priority
  • run python3 scripts/find_secrets.py . and show me what it finds

How to install security-auditor

1Skills CLI (Vercel)

npx skills add zhaono1/agent-playbook --skill security-auditor -a claude-code

2Manually: put the files in place

~/.claude/skills/security-auditor/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/security-auditor/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about security-auditor

How do I install security-auditor in Claude?

Run npx skills add zhaono1/agent-playbook --skill security-auditor -a claude-code. The skill lands in ~/.claude/skills/security-auditor/SKILL.md.

What does security-auditor do?

It looks for vulnerabilities across the OWASP Top 10:2025 — access control, misconfiguration, supply chain, cryptography, injection, authentication, logging and exceptional conditions. It also checks code, config and dependencies against a checklist.

What does the skill need to work?

Python 3 in your environment, because both scripts run through python3. You also need access to the project's source and config files, otherwise there is nothing to audit.

Source text

SKILL.md · MIT
---
name: security-auditor
description: Security vulnerability expert covering OWASP Top 10 and common security issues. Use when conducting security audits or reviewing code for vulnerabilities.
allowed-tools: Read, Grep, Glob, Bash, WebSearch
metadata:
  hooks:
    after_complete:
      - trigger: self-improving-agent
        mode: background
        reason: "Learn from security patterns"
      - trigger: session-logger
        mode: auto
        reason: "Log security audit"
---

# Security Auditor

Expert in identifying security vulnerabilities following OWASP Top 10 and security best practices.

## When This Skill Activates

Activates when you:
- Request a security audit
- Mention "security" or "vulnerability"
- Need security review
- Ask about OWASP

## OWASP Top 10:2025 Coverage

Use the current OWASP Top 10 as an awareness taxonomy, not as proof of complete
security coverage. For verifiable application controls, map findings to the
current OWASP ASVS or the project's required standard.

### A01: Broken Access Control

- Verify authentication and object/function-level authorization on every sensitive path.
- Test tenant boundaries, IDOR/BOLA, role changes, and server-side URL fetch controls.
- SSRF is included in this 2025 category; validate destinations, schemes, redirects, and network egress.

### A02: Security Misconfiguration

- Inspect debug flags, CORS, security headers, default accounts, cloud/IaC policy, and error exposure.
- Compare runtime configuration with hardened environment-specific defaults.

### A03: Software Supply Chain Failures

- Review lockfiles, provenance, build workflows, mutable CI dependencies, update policy, and dependency risk.
- Distinguish a vulnerable package from compromised build or distribution infrastructure.

### A04: Cryptographic Failures

- Check secret storage, transport encryption, key lifecycle, random generation, algorithms, and data-at-rest requirements.
- Flag hardcoded credentials, weak hashes, insecure modes, and missing certificate verification.

### A05: Injection

- Trace untrusted data into SQL/NoSQL, shell, template, LDAP, expression, and browser execution sinks.
- Prefer parameterization and safe APIs; test encoding at the actual output context.

### A06: Insecure Design

- Threat-model trust boundaries, abuse cases, rate limits, high-risk workflows, and failure recovery.
- Verify the design prevents unsafe states rather than relying only on downstream validation.

### A07: Authentication Failures

- Review credential handling, MFA where risk warrants it, reset/recovery flows, session rotation, expiry, and brute-force defenses.

### A08: Software or Data Integrity Failures

- Verify signatures, trusted update channels, deserialization boundaries, artifact integrity, and protection from unauthorized data changes.

### A09: Security Logging and Alerting Failures

- Check that security-relevant events are logged without secrets, protected from tampering, monitored, and connected to actionable alerts.

### A10: Mishandling of Exceptional Conditions

- Exercise malformed input, resource exhaustion, timeouts, partial failures, concurrency, and dependency outages.
- Look for fail-open behavior, swallowed errors, unsafe retries, inconsistent state, and missing rollback or reconciliation.

## Security Audit Checklist

### Code Review
- [ ] No hardcoded secrets
- [ ] Input validation on all inputs
- [ ] Output encoding for XSS prevention
- [ ] Parameterized queries for SQL
- [ ] Proper error handling
- [ ] Authentication on protected routes
- [ ] Authorization checks
- [ ] Rate limiting on public APIs

### Configuration
- [ ] Debug mode off
- [ ] HTTPS enforced
- [ ] CORS configured correctly
- [ ] Security headers set
- [ ] Environment variables for secrets
- [ ] Database not exposed

### Dependencies
- [ ] No known vulnerabilities
- [ ] Dependencies up to date
- [ ] Unused dependencies removed

## Scripts

Run security audit:
```bash
python3 scripts/security_audit.py --name <service-name> --output security-audit.md
```

Check for secrets:
```bash
python3 scripts/find_secrets.py .
```

## References

- `references/owasp.md` - OWASP Top 10 details
- `references/checklist.md` - Security audit checklist
- `references/remediation.md` - Vulnerability remediation guide

© zhaono1 · MIT · zhaono1/agent-playbook

Similar skills

Everything for Security →

security-auditor by other authors comes first.

security-auditor sickn33 Turns your AI coder into a security expert: conducts audits, analyzes vulnerabilities, reviews SDLC and compliance with OWASP, GDPR, PCI-DSS standards. CX Codex +1 1,400installs security-auditor ovachiever Scans your code for OWASP Top 10 patterns: SQL injection, XSS, exposed secrets, broken auth. Fires on file changes and before deployments. CX Codex +1 780installs Python Security Vulnerability Auditor (OWASP-Mapped & Production-Hardened) sivasaiyadav8143 A prompt that audits Python code: it lists vulnerabilities, maps them to the OWASP Top 10, and returns a hardened rewrite. GP ChatGPT ★ 174,597repo stars security boshu2 Reviews code, dependencies and prompt surfaces for weaknesses. Useful when you need to know whether code is safe to ship. CX Codex +1 1,400installs security-scan jwynia Scans a codebase for OWASP Top 10 flaws, hardcoded credentials and unsafe configs. Useful before a deploy or when reading unfamiliar code. CX Codex +1 471installs setup-auditor UseAI-pro Checks an OpenClaw environment for leaked credentials, unsafe defaults and missing sandbox controls. Returns a report with a readiness verdict and a fix checklist. CX Codex +1 469installs Next.js Security Scan sugarforever A skill that scans Next.js and TypeScript/JavaScript projects for XSS, injection flaws, auth holes and hardcoded secrets. Useful before you ship. CX Codex +1 553installs vibe-security Chris Raroque A skill that audits apps built fast with an AI assistant: leaked keys, broken database access rules, and trust placed in values coming from the client. CX Codex +1 3,600installs

From the same set18

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor