security-skills MCP — Casos de uso, Instalar & Demo ao vivo

Por que usar

Principais recursos

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

Demo ao vivo

Como fica na prática

security-skill.replay ▶ pronto

0/0

Instalar

Escolha seu cliente

~/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
    }
  }
}

Abra Claude Desktop → Settings → Developer → Edit Config. Reinicie após salvar.

~/.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 usa o mesmo esquema mcpServers que o Claude Desktop. Config de projeto vence a global.

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

Clique no ícone MCP Servers na barra lateral do Cline, depois "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
    }
  }
}

Mesmo formato do Claude Desktop. Reinicie o Windsurf para aplicar.

~/.continue/config.json

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

O Continue usa um array de objetos de servidor em vez de um map.

~/.config/zed/settings.json

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

Adicione em context_servers. Zed recarrega automaticamente ao salvar.

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

Uma linha só. Verifique com claude mcp list. Remova com claude mcp remove.

Casos de uso

Usos do mundo real: security-skills

Produce a STRIDE threat model for a new feature

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

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

Pré-requisitos

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

Fluxo

Walk the system

Use security-skills. Here's the design for [feature]. Enumerate trust boundaries and data flows.✓ Copiado

→ Named trust boundaries, explicit data flow arrows
Apply STRIDE

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

→ Table with threats scored, not generic 'consider XSS'
Propose mitigations

Rank the threats by likelihood * impact and propose concrete mitigations for the top 5.✓ Copiado

→ Specific controls (rate limit, signed requests, audit log)

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

Armadilhas

STRIDE becomes checkbox theater — Demand concrete attacker stories — 'attacker with X wants Y, does Z'

Combine com: filesystem

Sweep a repo's dependencies for known CVEs

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

Quando usar: A new CVE drops and you need to know where you're exposed.

Fluxo

Point at the manifest

Use security-skills. Audit package-lock.json for dependencies with known CVEs published in the last 90 days.✓ Copiado

→ List of packages, advisory IDs, severity
Triage by usage

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

→ Reachable vs unreachable classification
Draft an upgrade plan

Plan the minimum-risk upgrade order so CI doesn't explode.✓ Copiado

→ Ordered upgrade sequence with version pins

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

Armadilhas

Transitive dependencies missed — Use full lockfile, not just top-level manifest

Combine com: filesystem · github

Review Terraform and k8s manifests for common misconfigs

👤 Platform engineers, DevSecOps ⏱ ~30 min intermediate

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

Fluxo

Point Claude at the IaC directory

Use security-skills. Scan terraform/ for S3 buckets without encryption, IAM wildcards, public security groups.✓ Copiado

→ File+line references with severity
Get fixes

For each finding, propose the minimal Terraform diff to fix it.✓ Copiado

→ HCL snippets showing before/after

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

Armadilhas

False positives on intentional public assets — Tag resources that are intentionally public; the skill should skip them

Combine com: github · filesystem

Combinações

Combine com outros MCPs para 10× de alavancagem

security-skill + github

Post findings as PR comments automatically

Review this PR and leave line comments for each security finding.✓ Copiado

security-skill + filesystem

Recursive scans across a monorepo

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

Ferramentas

O que este MCP expõe

Ferramenta	Entradas	Quando chamar	Custo
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

Custo e limites

O que custa rodar

Cota de API: None built-in
Tokens por chamada: Moderate — depends on files inspected
Monetário: Free
Dica: Scope scans to specific directories; don't point at node_modules.

Segurança

Permissões, segredos, alcance

Armazenamento de credenciais: None in skill itself

Saída de dados: 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'.

Solução de problemas

Erros comuns e correções

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.

Alternativas

security-skills vs. outros

Alternativa	Quando usar	Troca
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

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills