/ Verzeichnis / Playground / Transilience Community Tools
← Alle Server ↗ GitHub
● Community transilienceai ⚡ Sofort

Transilience Community Tools

von transilienceai · transilienceai/communitytools

Open-source Claude Code skills, agents, and slash commands for AI-powered pentesting, bug bounty, and security research.

Transilience Community Tools is a Claude skill / skill pack maintained by transilienceai. Open-source Claude Code skills, agents, and slash commands for AI-powered pentesting, bug bounty, and security research. See README for installation and configuration: https://github.com/transilienceai/communitytools

▶ Demo ansehen 📦 Installieren 💡 Anwendungsfälle

Warum nutzen

Hauptfunktionen

Live-Demo

In der Praxis

transilience-communitytools.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": {
    "transilience-communitytools": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/transilienceai/communitytools",
        "~/.claude/skills/communitytools"
      ],
      "_inferred": true
    }
  }
}

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

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "transilience-communitytools": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/transilienceai/communitytools",
        "~/.claude/skills/communitytools"
      ],
      "_inferred": true
    }
  }
}

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

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "transilience-communitytools": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/transilienceai/communitytools",
        "~/.claude/skills/communitytools"
      ],
      "_inferred": true
    }
  }
}

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

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "transilience-communitytools": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/transilienceai/communitytools",
        "~/.claude/skills/communitytools"
      ],
      "_inferred": true
    }
  }
}

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

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "transilience-communitytools",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/transilienceai/communitytools",
        "~/.claude/skills/communitytools"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json
{
  "context_servers": {
    "transilience-communitytools": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/transilienceai/communitytools",
          "~/.claude/skills/communitytools"
        ]
      }
    }
  }
}

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

claude mcp add transilience-communitytools -- git clone https://github.com/transilienceai/communitytools ~/.claude/skills/communitytools

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

Anwendungsfälle

Praxisnahe Nutzung: Transilience Community Tools

Use Transilience Community Tools for its primary workflow

👤 Claude Code users ⏱ ~20 min intermediate

Wann einsetzen: See repo README for canonical use cases.

Voraussetzungen
  • Repo cloned or installed — See https://github.com/transilienceai/communitytools
Ablauf
  1. Install
    Install Transilience Community Tools per README.✓ Kopiert
    → Skill registered with client
  2. Configure
    Provide credentials/config as instructed.✓ Kopiert
    → Successful auth/init
  3. Use
    Run a sample task with Transilience Community Tools.✓ Kopiert
    → Expected output

Ergebnis: You can drive the documented workflow end-to-end.

Fallstricke
  • Skipping README — Read the repo README and CHANGELOG before shipping to prod.

Werkzeuge

Was dieses MCP bereitstellt

WerkzeugEingabenWann aufrufenKosten
primary see README Primary action free

Kosten & Limits

Was der Betrieb kostet

API-Kontingent
None of its own; bounded by upstream provider quotas if any
Tokens pro Aufruf
Depends on usage
Kosten in €
Open source — check repo LICENSE
Tipp
Review upstream API costs (if any) before automating.

Sicherheit

Rechte, Secrets, Reichweite

Minimale Scopes: Whatever the upstream provider requires
Credential-Speicherung: Env vars or local config — never commit secrets
Datenabfluss: Forwards data per its README
Niemals gewähren: Full admin to untrusted prompts

Fehlerbehebung

Häufige Fehler und Lösungen

Auth fails

Verify credentials and required scopes match README.

Prüfen: Re-read repo README auth section.
Tool not found by client

Ensure MCP client config points to correct command/path.

Prüfen: Restart the client after editing config.

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen