/ ディレクトリ / プレイグラウンド / security-skills
← 全サーバー ↗ GitHub
● コミュニティ eth0izzle ⚡ 即起動

security-skills

作者 eth0izzle · eth0izzle/security-skills

Defensive security skills for Claude Code — threat modeling, config review, dependency audits. For blue teams, not pentesters.

A collection of Claude Code skills oriented around defensive security work: reviewing IAM policies, checking dependency trees for known CVEs, producing threat models for new features, auditing Dockerfiles and k8s manifests for common misconfigurations.

▶ デモを見る 📦 インストール 💡 ユースケース

なぜ使うのか

主な機能

ライブデモ

実際の動作

security-skill.replay ▶ 準備完了
0/0

インストール

作者のリポジトリ · Claude Skills の公式ドキュメント

ユースケース

実用的な使い方： security-skills

Produce a STRIDE threat model for a new feature

👤 Security engineers, staff+ engineers owning a feature's security review ⏱ ~45 min advanced

使うタイミング： Design review for a feature that touches user data, auth, or external networks.

フロー
  1. Walk the system
    Use security-skills. Here's the design for [feature]. Enumerate trust boundaries and data flows.✓ コピーしました
    → Named trust boundaries, explicit data flow arrows
  2. Apply STRIDE
    For each boundary, call out Spoofing, Tampering, Repudiation, Info Disclosure, DoS, Elevation risks.✓ コピーしました
    → Table with threats scored, not generic 'consider XSS'
  3. Propose mitigations
    Rank the threats by likelihood * impact and propose concrete mitigations for the top 5.✓ コピーしました
    → Specific controls (rate limit, signed requests, audit log)

結果： A threat model doc ready for a security review meeting.

注意点
  • STRIDE becomes checkbox theater — Demand concrete attacker stories — 'attacker with X wants Y, does Z'
組み合わせ： filesystem

Sweep a repo's dependencies for known CVEs

👤 Dev teams responding to a security advisory ⏱ ~30 min intermediate

使うタイミング： A new CVE drops and you need to know where you're exposed.

フロー
  1. Point at the manifest
    Use security-skills. Audit package-lock.json for dependencies with known CVEs published in the last 90 days.✓ コピーしました
    → List of packages, advisory IDs, severity
  2. Triage by usage
    For each vulnerable dep, grep the codebase — is it actually reachable?✓ コピーしました
    → Reachable vs unreachable classification
  3. Draft an upgrade plan
    Plan the minimum-risk upgrade order so CI doesn't explode.✓ コピーしました
    → Ordered upgrade sequence with version pins

結果： A concrete patch plan — not 'run npm audit fix' and pray.

注意点
  • Transitive dependencies missed — Use full lockfile, not just top-level manifest
組み合わせ： filesystem · github

Review Terraform and k8s manifests for common misconfigs

👤 Platform engineers, DevSecOps ⏱ ~30 min intermediate

使うタイミング： Before merging IaC changes into main, or auditing what's already there.

フロー
  1. Point Claude at the IaC directory
    Use security-skills. Scan terraform/ for S3 buckets without encryption, IAM wildcards, public security groups.✓ コピーしました
    → File+line references with severity
  2. Get fixes
    For each finding, propose the minimal Terraform diff to fix it.✓ コピーしました
    → HCL snippets showing before/after

結果： PR-sized security fixes you can merge incrementally.

注意点
  • False positives on intentional public assets — Tag resources that are intentionally public; the skill should skip them
組み合わせ： github · filesystem

組み合わせ

他のMCPと組み合わせて10倍の力を

security-skill + github

Post findings as PR comments automatically

Review this PR and leave line comments for each security finding.✓ コピーしました
security-skill + filesystem

Recursive scans across a monorepo

Walk the entire services/ tree and aggregate findings by service.✓ コピーしました

ツール

このMCPが提供する機能

ツール入力呼び出すタイミングコスト
threat_model system description Design-phase review 0
cve_audit lockfile path After a public CVE drops 0 (uses public advisory data)
iac_review directory path Pre-merge IaC audits 0
secret_scan path or diff Pre-commit or pre-push 0

コストと制限

運用コスト

APIクォータ
None built-in
呼び出しあたりのトークン
Moderate — depends on files inspected
金額
Free
ヒント
Scope scans to specific directories; don't point at node_modules.

セキュリティ

権限、シークレット、影響範囲

認証情報の保管： None in skill itself
データ送信先： None — skill is prompts; be aware inspected code goes to Claude API

トラブルシューティング

よくあるエラーと対処法

Skill suggests exploitation techniques

Re-prompt for defensive framing: 'as a defender, how do I prevent X'

Too many false positives on IaC scan

Provide context (prod vs staging; intentional public resources)

Missed a known vulnerability

Claude's knowledge cutoff may lag. Pair with a proper scanner (Trivy, Snyk) for authoritative CVE data.

代替案

security-skills 他との比較

代替案代わりに使う場面トレードオフ
Trivy / GrypeYou need an authoritative, up-to-date vulnerability databaseNo LLM reasoning — just raw scan output
tfsec / checkovSpecific IaC scanning with a curated rule setRule-bound; misses nuanced misconfigs

その他

リソース

📖 GitHub の公式 README を読む

🐙 オープンな issue を見る

🔍 400以上のMCPサーバーとSkillsを見る