/ Annuaire / Playground / security-skills
← Tous les serveurs ↗ GitHub
● Communauté eth0izzle ⚡ Instantané

security-skills

par 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.

▶ Voir la démo 📦 Installer 💡 Cas d'usage

Pourquoi l'utiliser

Fonctionnalités clés

Démo en direct

Aperçu en pratique

security-skill.replay ▶ prêt
0/0

Installation

Dépôt de l’auteur · Documentation officielle des Skills Claude

Cas d'usage

Usages concrets : security-skills

Produce a STRIDE threat model for a new feature

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

Quand l'utiliser : Design review for a feature that touches user data, auth, or external networks.

Déroulement
  1. Walk the system
    Use security-skills. Here's the design for [feature]. Enumerate trust boundaries and data flows.✓ Copié
    → Named trust boundaries, explicit data flow arrows
  2. Apply STRIDE
    For each boundary, call out Spoofing, Tampering, Repudiation, Info Disclosure, DoS, Elevation risks.✓ Copié
    → 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.✓ Copié
    → Specific controls (rate limit, signed requests, audit log)

Résultat : A threat model doc ready for a security review meeting.

Pièges
  • STRIDE becomes checkbox theater — Demand concrete attacker stories — 'attacker with X wants Y, does Z'
Combiner avec : filesystem

Sweep a repo's dependencies for known CVEs

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

Quand l'utiliser : A new CVE drops and you need to know where you're exposed.

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

Résultat : A concrete patch plan — not 'run npm audit fix' and pray.

Pièges
  • Transitive dependencies missed — Use full lockfile, not just top-level manifest
Combiner avec : filesystem · github

Review Terraform and k8s manifests for common misconfigs

👤 Platform engineers, DevSecOps ⏱ ~30 min intermediate

Quand l'utiliser : Before merging IaC changes into main, or auditing what's already there.

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

Résultat : PR-sized security fixes you can merge incrementally.

Pièges
  • False positives on intentional public assets — Tag resources that are intentionally public; the skill should skip them
Combiner avec : github · filesystem

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

security-skill + github

Post findings as PR comments automatically

Review this PR and leave line comments for each security finding.✓ Copié
security-skill + filesystem

Recursive scans across a monorepo

Walk the entire services/ tree and aggregate findings by service.✓ Copié

Outils

Ce que ce MCP expose

OutilEntréesQuand appelerCoût
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

Coût et limites

Coût d'exécution

Quota d'API
None built-in
Tokens par appel
Moderate — depends on files inspected
Monétaire
Free
Astuce
Scope scans to specific directories; don't point at node_modules.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : None in skill itself
Sortie de données : None — skill is prompts; be aware inspected code goes to Claude API

Dépannage

Erreurs courantes et correctifs

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.

Alternatives

security-skills vs autres

AlternativeQuand l'utiliserCompromis
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

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills