A collection of cybersecurity skills for AI coding agents. The AI does the heavy lifting; you bring the context about your stack and your priorities.
Built to be useful at every experience level:
- Security engineers and pentesters running formal audits — concrete grep patterns, OWASP / NIST / ATT&CK alignment, report templates that pass auditor review
- Developers shipping safer code without a dedicated security team to lean on — security work that fits into a normal sprint, plain-English explanations of why each finding matters
- Founders, ops folks, and small-team operators securing a stack they can't afford a CISO for — guided, opinionated playbooks for the most common security work, with the audit skill explaining what it found and why
- Red / blue / purple teams running real engagements — offensive recon, web pentest, threat hunting, detection engineering, SOC operations
You do not need to be a security expert to use these skills. The skills are written so the AI agent can run them end-to-end and explain the findings in language any technical reader can follow. If you can describe what you have and what you want to know about it, the agent can do the work.
Skills are authored as Claude Code SKILL.md files (the canonical format) and built into adapters for Cursor and Codex. Installable via npx skills or the Claude Code plugin marketplace.
Built by Bri Russell. I run real audits with these skills, then bring the gaps I find back into the skill itself — so each version is a little less opinion and a little more evidence.
Contributions welcome! Field feedback is the most valuable contribution — whether you're a security engineer who hit a gap during an audit, a developer whose AI agent missed something obvious, or a founder who used a skill and got an answer that wasn't quite right. Open a PR or open an issue — every level of expertise produces useful signal.
Not every skill is for every user on day one. A good starting point by context:
- Reviewing your own code or product: start with
owasp-auditfor the source-code sweep, thenapi-auditif you have API endpoints, thendependency-auditfor the CVE pass - Securing cloud / infrastructure: start with
cloud-audit(AWS / GCP / Azure misconfig), theniam-auditif you manage identities, thencontainer-auditif you run Docker / Kubernetes - Responding to "something happened":
incident-triagefor the immediate response,disk-forensicsif you need to analyze a system afterward,security-commsto draft the stakeholder / customer communications - Building a security program from scratch:
csf-mappingfor the governance frame,threat-modelingbefore new features,breach-patternsto learn from public incidents - Working under a specific regulation:
privacy-engineeringfor GDPR / CCPA / similar privacy laws,hipaa-auditfor ePHI,pci-auditfor payment cards,ai-risk-managementfor AI features - Closing the loop on findings:
finding-triagefor any single finding from any source — gives you a defensible disposition with the right ticket fields - Translating security work upward or outward:
security-commsfor board / exec / customer / engineering / sales-engineering deliverables
The offensive skills (recon, osint-recon, web-pentest, red-team-engagement) require explicit authorization for the target and assume more security context. They open with an authorization check and will refuse anything ambiguous. red-team-engagement in particular carries the strongest refusal posture in the catalog and will refuse to plan anything against systems the user cannot demonstrate authorization for.
Skills are markdown files that give AI agents specialized knowledge and workflows for specific tasks. Drop them into your project and your agent recognizes when you're working on a security task and applies the right methodology — OWASP categories, NIST IR steps, MITRE ATT&CK references, the actual grep patterns that surface the bug.
The goal isn't to replace a security engineer — or to pretend you have one if you don't. It's to give the agent enough structure that the first pass is useful, the report format is consistent, and the obvious stuff stops slipping through. For teams without dedicated security headcount, that closes a real gap. For teams with security engineers, it lets them spend their time on the work the AI can't do.
The skills are organized into seven families. Most security work crosses families — an OWASP audit surfaces a dependency question, an incident kicks off an OSINT trail, cloud findings overlap with appsec, and findings have to be translated for the audience that hears them. Skills cross-reference each other where that's true; finding-triage, security-comms, and csf-mapping orchestrate across the whole map.
┌──────────────────────────────────────────┐
│ Cybersecurity Skill Map │
└──────────────────────┬───────────────────┘
│
┌──────────┬──────────┬──────────┬───────┴────┬─────────┬──────────┬───────────┐
▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼
┌──────┐ ┌────────┐ ┌────────┐ ┌────────┐ ┌──────┐ ┌─────────┐ ┌──────────┐
│AppSec│ │Offens. │ │Detect &│ │Cloud & │ │ AI │ │Design & │ │Complianc │
│& Sup │ │& Recon │ │Respond │ │ Infra │ │Secur.│ │Governnce│ │& Privacy │
├──────┤ ├────────┤ ├────────┤ ├────────┤ ├──────┤ ├─────────┤ ├──────────┤
│owasp-│ │recon │ │incid- │ │cloud- │ │promp-│ │threat- │ │privacy- │
│ audit│ │osint- │ │ triage │ │ audit │ │ inj. │ │ modeling│ │ engineer-│
│api- │ │ recon │ │disk- │ │contain-│ │ai- │ │vuln- │ │ ing │
│ audit│ │web- │ │ forens.│ │ audit │ │ risk-│ │ research│ │pci-audit │
│depen-│ │ pentest│ │siem- │ │iam-aud-│ │ mgmt │ │finding- │ │hipaa- │
│ audit│ │red- │ │ detect.│ │ it │ │ │ │ triage │ │ audit │
│secre-│ │ team- │ │soc- │ │ │ │ │ │csf- │ │ │
│ audit│ │ engage-│ │ ops │ │ │ │ │ │ mapping │ │ │
│crypt-│ │ ment │ │threat- │ │ │ │ │ │security-│ │ │
│ audit│ │ │ │ hunting│ │ │ │ │ │ comms │ │ │
│mobile│ │ │ │breach- │ │ │ │ │ │ │ │ │
│-audit│ │ │ │patterns│ │ │ │ │ │ │ │ │
└──┬───┘ └───┬────┘ └───┬────┘ └───┬────┘ └──┬───┘ └────┬────┘ └────┬─────┘
│ │ │ │ │ │ │
└─────────┴────┬─────┴──────────┴─────────┴───────────┴────────────┘
│
Common crossovers:
owasp-audit ↔ api-audit ↔ dependency-audit ↔ vuln-research
web-pentest ↔ recon ↔ osint-recon ↔ red-team-engagement
siem-detection → threat-hunting → incident-triage → disk-forensics
cloud-audit ↔ container-audit ↔ iam-audit ↔ secrets-audit
threat-modeling → owasp-audit / api-audit (pre-implementation → code)
prompt-injection ⇆ ai-risk-management (security slice ⇆ whole lifecycle)
privacy-engineering ⇆ hipaa-audit / pci-audit (engineering ⇆ regulatory)
breach-patterns → every audit skill (what to check)
finding-triage ← every audit skill (closes the loop on any finding)
security-comms ← every skill (translates output for non-security audience)
csf-mapping ← every skill (rolls evidence into governance frame)
| Skill | What it does |
|---|---|
| ai-risk-management | NIST AI Risk Management Framework + EU AI Act — model lifecycle governance, fairness, robustness, transparency, monitoring, third-party model risk. Broader than prompt-injection. |
| api-audit | OWASP API Security Top 10 (2023) — REST / GraphQL / RPC endpoint audit. BOLA, mass assignment, BFLA, rate-limit, GraphQL introspection, webhook signature. |
| breach-patterns | Preemptive hardening — read public breach disclosures, extract the audit question each one implies, check your stack. Capital One / LastPass / Okta / Snowflake / MOVEit / Codecov / Equifax / Uber. |
| cloud-audit | AWS / GCP / Azure infrastructure misconfiguration, excessive IAM, public exposure, compliance gaps. |
| container-audit | Docker + Kubernetes audit. Dockerfile, base images, pod security, RBAC, NetworkPolicy, secrets, image policy, runtime. |
| crypto-audit | Cryptography implementation review — algorithm/mode choice, KDF parameters, IV/nonce handling, authenticated encryption, signature verification, randomness, TLS posture, key lifecycle. Deeper than owasp-audit A02. |
| csf-mapping | NIST CSF 2.0 posture assessment — Govern / Identify / Protect / Detect / Respond / Recover. Subcategory mapping, current/target tiers, prioritized roadmap. Translates technical findings into governance language. |
| dependency-audit | Dependencies, frameworks, runtimes, toolchain — CVEs, security anti-patterns, supply chain risk. |
| disk-forensics | Disk image analysis, evidence recovery, timeline reconstruction. Explicit Authorization Check covering lawful basis, chain of custody, privacy scope. |
| finding-triage | Single-finding disposition workflow — Fixed / Deferred / Accepted Risk / False Positive, with ticket-ready writeup templates and required-field enforcement. Closes the loop on every audit skill. |
| hipaa-audit | HIPAA Security / Privacy / Breach Notification — three safeguard categories, 18 identifiers, BAA chain-of-liability, minimum-necessary, 60-day breach clock, encryption-as-safe-harbor. |
| iam-audit | Consultant-style IAM — audit / design / migrate. Cloud IAM (AWS/GCP/Azure), identity providers (Okta/Entra/Auth0/Workspace), application authorization (RBAC/ABAC/ReBAC), workload identity, JIT access, break-glass. |
| incident-triage | Security incident triage following NIST SP 800-61. |
| mobile-audit | iOS + Android audit against OWASP MASVS / MASTG — storage, crypto, network, auth, platform IPC, code, resilience. |
| osint-recon | Open source intelligence gathering and correlation. |
| owasp-audit | Source-code audit against OWASP Top 10 (2021) — category checklist, grep patterns, runtime verification, Second-Opinion Pass, three-disposition reporting. |
| pci-audit | PCI DSS v4.0 — scope determination first, then Req 3 (CHD storage) / 4 (transmission) / 6 (secure SDLC) / 7-8 (access) / 10 (logging) / 11 (testing) / 12 (program). |
| privacy-engineering | GDPR / CCPA / CPRA / LGPD / PIPEDA technical implementation — data classification, minimization, consent, the DSAR pipeline (access / deletion / portability with full vendor fan-out), DPIA inputs. |
| prompt-injection | AI features / LLM integrations / agents — prompt injection, privilege escalation, authorization bypass. |
| recon | Structured attack surface enumeration for authorized pentests, bug bounty, CTF. |
| red-team-engagement | Authorized adversary emulation methodology — distinct from web-pentest. Multi-week, objective-based, assumed-breach. Heaviest authorization framing in the catalog. |
| secrets-audit | Find leaked secrets (code, Git history, build artifacts, CI, frontend bundles) + audit secrets-management posture (rotation, scope, workload identity). |
| security-comms | Translate security work for non-security audiences — board, executive, engineering, customer success, customers, legal, procurement. Seven audience archetypes, six templates (incident comms, post-mortem, breach disclosure, etc.). |
| siem-detection | SIEM detection engineering — log source coverage, Sigma rule authoring, MITRE ATT&CK mapping, FP tuning, detection-as-code. |
| soc-operations | Build / run / improve a SOC — alert prioritization, runbook authoring, escalation criteria, on-call structure, KPIs (MTTD / MTTR / FP rate), alert-fatigue tuning loop. |
| threat-hunting | Proactive, hypothesis-driven adversary detection — PEAK framework, ATT&CK-driven hunt catalog, every hunt produces an artifact (rule, dead-end doc, or coverage gap). |
| threat-modeling | Pre-implementation security design — STRIDE per element + abuse cases, data flow diagrams with trust boundaries, four-question Shostack frame. |
| vuln-research | CVE deep-dive — pull canonical sources, confirm versions, reachability analysis, check public PoCs / CISA KEV / EPSS, decide patch / mitigate / accept-risk. |
| web-pentest | Live web application pentest against an authorized target — OWASP WSTG-structured, nine phases from config through business logic. |
Every offensive skill enforces an authorization check before doing anything; every skill refuses destructive or unauthorized use. Details in Ethics & Authorization.
The vercel-labs/skills installer reads the canonical skills/ directory directly:
# List available skills
npx skills add briiirussell/cybersecurity-skills --list
# Install all skills
npx skills add briiirussell/cybersecurity-skills
# Install specific skills
npx skills add briiirussell/cybersecurity-skills --skill owasp-audit api-auditInstalls to your .agents/skills/ directory with a symlink into .claude/skills/ for Claude Code compatibility.
/plugin marketplace add briiirussell/cybersecurity-skills
/plugin install cybersecurity-skillsgit clone https://github.com/briiirussell/cybersecurity-skills.git
cp -r cybersecurity-skills/skills/owasp-audit .claude/skills/Trigger naturally ("run an OWASP audit on this codebase") or invoke directly with /owasp-audit.
cp -r cybersecurity-skills/skills/owasp-audit ~/.claude/skills/cp adapters/cursor/owasp-audit.mdc .cursor/rules/cp adapters/codex/owasp-audit.md <your-codex-config-dir>/git submodule add https://github.com/briiirussell/cybersecurity-skills.git .agents/cybersecurity-skillsThen reference skills from .agents/cybersecurity-skills/skills/.
After creating or modifying a skill, regenerate the Cursor + Codex adapters:
node scripts/build-adapters.mjs- Copy
templates/skill-template.mdtoskills/<your-skill>/SKILL.md - Fill in the frontmatter (
name,description,allowed-tools) - Write instructions in imperative form, under 500 lines
- Run the build script to generate adapters
Format details and writing guidance live in CLAUDE.md. Full contribution flow in CONTRIBUTING.md.
These skills are for authorized security testing, CTF competitions, security research, and defensive use only. Every offensive skill (recon, osint-recon, web-pentest, etc.) opens with an authorization check and refuses destructive techniques, mass targeting, supply-chain compromise, or evasion patterns intended for malicious use.
If you're using these against a system you don't own or have explicit written authorization to test, you are using them wrong. Don't.
This repo follows semantic versioning. See VERSIONS.md for the full changelog and GitHub Releases for release notes.
- MAJOR (X.0.0) — Breaking changes: skill renames, removals, or frontmatter changes that break existing installs
- MINOR (1.X.0) — New skill, or substantive expansion of an existing one
- PATCH (1.0.X) — Content fixes, grep-pattern updates, small additions
See CONTRIBUTING.md. The short version: field feedback (PRs or issues with concrete patterns from a real audit) is the highest-signal contribution. If a skill missed something in your audit, that's exactly what I want to know.
MIT — see LICENSE.