MCPInstall

security-auditor

Security vulnerability expert covering OWASP Top 10 and common security issues. Use when conducting security audits or reviewing code for vulnerabilities.

Installs
1.1K
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/zhaono1/agent-playbook --skill security-auditor
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads security-auditor automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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:

python3 scripts/security_audit.py --name <service-name> --output security-audit.md

Check for secrets:

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

FAQ

What does the security-auditor skill do?

Security vulnerability expert covering OWASP Top 10 and common security issues. Use when conducting security audits or reviewing code for vulnerabilities.

How do I install security-auditor?

Run npx skills add https://github.com/zhaono1/agent-playbook --skill security-auditor in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/security-auditor/ (personal) or .claude/skills/security-auditor/ (project).

Which AI agents can use security-auditor?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is security-auditor safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains security-auditor?

It is published by zhaono1 in zhaono1/agent-playbook. It has 1,050 recorded installs.

More from zhaono1/agent-playbook

View all →

self-improving-agent

zhaono1/agent-playbook

Use after a failure, user correction, repeated workflow problem, or validated success reveals a reusable lesson. Captures bounded redacted candidates, runs executable behavior evals, and separates validation from application in durable guidance.

AI & Agents35.1K installs

planning-with-files

zhaono1/agent-playbook

Uses persistent markdown files for general planning, progress tracking, and knowledge storage (Manus-style workflow). Use for multi-step tasks, research projects, or general organization WITHOUT mentioning PRD. For PRD-specific work, use prd-planner skill instead.

architecting-solutions

zhaono1/agent-playbook

Designs technical solutions and architecture. Use when user says "design solution", "architecture design", "technical design", or "方案设计" WITHOUT mentioning PRD. For PRD-specific work, use prd-planner skill instead.

skill-router

zhaono1/agent-playbook

Routes an agent request to the narrowest matching portable skill when the user asks which skill to use or needs help selecting one across supported hosts.

874 installs

workflow-orchestrator

zhaono1/agent-playbook

Coordinates multi-skill workflows and records or runs follow-up actions when the host runtime supports them. Use when completing PRD creation, implementation, or any milestone that should be evaluated for additional skills.

prd-planner

zhaono1/agent-playbook

Creates PRDs using persistent file-based planning. Use when user explicitly says "PRD", "product requirements document", or "产品需求文档". Combines PRD methodology with planning-with-files to avoid context switching.

Popular security skills

View category →

azure-compliance

microsoft/azure-skills

Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.

OfficialSecurity567K installs

minimal-run-and-audit

lllllllama/rigorpilot-skills

Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.

Security477.4K installs

seo-audit

coreyhaines31/marketingskills

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.

Security238.7K installs

firebase-security-rules-auditor

firebase/agent-skills

Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.

OfficialSecurity139.1K installs

audit

pbakaus/impeccable

Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.

Security81.9K installs

competitors

coreyhaines31/marketingskills

When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.

Security79.3K installs