AIコーディングエージェント向けのサイバーセキュリティスキルの集まり。AIが重労働を担い、スタックや優先事項の文脈をあなたが伝えます。

あらゆる経験レベルで役立つように作られています:

• セキュリティエンジニアおよびペンテスターが正式な監査を実施している — 具体的なGREPパターン、OWASP / NIST / ATT&CKの整合性、監査人レビューを通過するレポートテンプレート
• 開発者が専任のセキュリティチームなしで安全なコードを提供している — 通常のスプリントに収まるセキュリティ作業、各発見がなぜ重要かをわかりやすく説明する
• 創業者、オペレーション担当者、小規模チームのオペレーターがCISOを雇う余裕のないスタックのセキュリティを確保する場合 — 最も一般的なセキュリティ業務のためのガイド付き意見の多いプレイブック、監査スキルが何を発見し、なぜそうしたのかを説明する
• 赤/青/紫のチーム 実際の戦闘を実施 — 攻撃偵察、ウェブの浸透テスト、脅威ハンティング、探知エンジニアリング、SOC作戦

これらのスキルを使うのにセキュリティの専門家である必要はありません。これらのスキルは、AIエージェントがエンドツーエンドで実行し、技術的な読者なら理解できる言語で結果を説明できるように作成されています。

Cybersecurity Skills for AI Agents

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.

Where to start

Not every skill is for every user on day one. A good starting point by context:

• Not sure? Ask for security-start (or just say “where do I start with security?”). It asks two or three questions and picks the skill.
• Reviewing your own code or product: start with owasp-audit for the source-code sweep, then api-audit if you have API endpoints, then dependency-audit for the CVE pass
• A CVE wave just dropped and you run many apps: patch-sweep to work out which apps are affected and ship fixes across the fleet, with dependency-audit for each project