security-skills MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

Threat modeling template based on STRIDE
Dependency CVE cross-referencing workflow
IaC misconfiguration checks (Terraform, Docker, k8s)
Security code review patterns
Defensive focus — no exploitation tooling

Live-Demo

In der Praxis

security-skill.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "security-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/eth0izzle/security-skills",
        "~/.claude/skills/security-skills"
      ],
      "_inferred": true
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "security-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/eth0izzle/security-skills",
        "~/.claude/skills/security-skills"
      ],
      "_inferred": true
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "security-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/eth0izzle/security-skills",
        "~/.claude/skills/security-skills"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "security-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/eth0izzle/security-skills",
        "~/.claude/skills/security-skills"
      ],
      "_inferred": true
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "security-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/eth0izzle/security-skills",
        "~/.claude/skills/security-skills"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "security-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/eth0izzle/security-skills",
          "~/.claude/skills/security-skills"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add security-skill -- git clone https://github.com/eth0izzle/security-skills ~/.claude/skills/security-skills

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

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.

Voraussetzungen

Feature design doc or architecture diagram — Paste into chat or point Claude at the file
Skill installed — git clone https://github.com/eth0izzle/security-skills ~/.claude/skills/security-skills

Ablauf

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
Apply STRIDE

For each boundary, call out Spoofing, Tampering, Repudiation, Info Disclosure, DoS, Elevation risks.✓ Kopiert

→ Table with threats scored, not generic 'consider XSS'
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

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
Triage by usage

For each vulnerable dep, grep the codebase — is it actually reachable?✓ Kopiert

→ Reachable vs unreachable classification
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

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

Werkzeug	Eingaben	Wann aufrufen	Kosten
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

Defensive only. Do not use for exploitation, credential harvesting, or red-team operations.
Never paste production secrets into prompts — even when asking the skill to 'find them'.

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

Alternative	Wann stattdessen	Kompromiss
Trivy / Grype	You need an authoritative, up-to-date vulnerability database	No LLM reasoning — just raw scan output
tfsec / checkov	Specific IaC scanning with a curated rule set	Rule-bound; misses nuanced misconfigs

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen