/ Verzeichnis / Playground / security-skills
← Alle Server ↗ GitHub
● Community eth0izzle ⚡ Sofort

security-skills

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

▶ Demo ansehen 📦 Installieren 💡 Anwendungsfälle

Warum nutzen

Hauptfunktionen

Live-Demo

In der Praxis

security-skill.replay ▶ bereit
0/0

Installation

Repository des Autors · Offizielle Dokumentation zu Claude Skills

Anwendungsfälle

Praxisnahe Nutzung: security-skills

Produce a STRIDE threat model for a new feature

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

Wann einsetzen: Design review for a feature that touches user data, auth, or external networks.

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

Ergebnis: A threat model doc ready for a security review meeting.

Fallstricke
  • STRIDE becomes checkbox theater — Demand concrete attacker stories — 'attacker with X wants Y, does Z'
Kombinieren mit: filesystem

Sweep a repo's dependencies for known CVEs

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

Wann einsetzen: A new CVE drops and you need to know where you're exposed.

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

Ergebnis: A concrete patch plan — not 'run npm audit fix' and pray.

Fallstricke
  • Transitive dependencies missed — Use full lockfile, not just top-level manifest
Kombinieren mit: filesystem · github

Review Terraform and k8s manifests for common misconfigs

👤 Platform engineers, DevSecOps ⏱ ~30 min intermediate

Wann einsetzen: Before merging IaC changes into main, or auditing what's already there.

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

Ergebnis: PR-sized security fixes you can merge incrementally.

Fallstricke
  • False positives on intentional public assets — Tag resources that are intentionally public; the skill should skip them
Kombinieren mit: github · filesystem

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

security-skill + github

Post findings as PR comments automatically

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

Recursive scans across a monorepo

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

Werkzeuge

Was dieses MCP bereitstellt

WerkzeugEingabenWann aufrufenKosten
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

Kosten & Limits

Was der Betrieb kostet

API-Kontingent
None built-in
Tokens pro Aufruf
Moderate — depends on files inspected
Kosten in €
Free
Tipp
Scope scans to specific directories; don't point at node_modules.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: None in skill itself
Datenabfluss: None — skill is prompts; be aware inspected code goes to Claude API

Fehlerbehebung

Häufige Fehler und Lösungen

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.

Alternativen

security-skills vs. andere

AlternativeWann stattdessenKompromiss
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

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen