agentleFS
SHAdd0WTAkaSHAdd0WTAka/Zen-Ai-Pentest/.skills/SKILL.md

.skills

Skill470 starsChanged 4 months agoMITView on GitHub

Zen-AI-Pentest ist ein autonomes, KI-gesteuertes Penetration-Testing-Framework mit: - 1206+ Dateien, 179MB Repository - 58 GitHub Actions Workflows - 20+ integrierte Sicherheitstools - Multi-Agent-Architektur mit ReAct Pattern - FastAPI-Backend mit WebSocket-Support - React-Dashboard für Web-UI Kritische Workflows: - ci.yml - Haupt-CI - security.yml - Sicherheits-Scans - code-quality.yml - Linting & Formatting - pr-validation.yml - PR Checks - release.yml - Release-Prozess - deploy.yml - Deployment Auto-Workflows: - dependabot-auto-merge.yml - Automatische Dependency-Updates - auto-fix-repository.yml - Automatische Fixes - health-check.yml - Repository-Health

  • Installs packages

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Hardcoded Credentials: - Default-Credentials in API auth fallback

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Zen-AI-Pentest Development Skills

Projekt-Übersicht

Zen-AI-Pentest ist ein autonomes, KI-gesteuertes Penetration-Testing-Framework mit:

  • 1206+ Dateien, 179MB Repository
  • 58 GitHub Actions Workflows
  • 20+ integrierte Sicherheitstools
  • Multi-Agent-Architektur mit ReAct Pattern
  • FastAPI-Backend mit WebSocket-Support
  • React-Dashboard für Web-UI

Architektur

┌─────────────────────────────────────────────────────────┐
│  FRONTEND (React + TypeScript + Tailwind)               │
├─────────────────────────────────────────────────────────┤
│  API LAYER (FastAPI + WebSocket + JWT Auth)             │
├─────────────────────────────────────────────────────────┤
│  AUTONOMOUS LAYER (ReAct Agent + Memory + Tool Exec)    │
├─────────────────────────────────────────────────────────┤
│  RISK ENGINE (CVSS + EPSS + False Positive Reduction)   │
├─────────────────────────────────────────────────────────┤
│  TOOLS LAYER (Nmap, SQLMap, Metasploit, etc.)           │
├─────────────────────────────────────────────────────────┤
│  DATA LAYER (PostgreSQL + SQLite + Redis)               │
└─────────────────────────────────────────────────────────┘

Kritische Issues (P0)

  1. Command Injection Risk - tool_executor.py nutzt subprocess_shell statt subprocess_exec
  2. Variable Bug - react_agent_vm.py: config.vm_username sollte self.vm_config.vm_username sein
  3. Hardcoded Credentials - Default-Credentials in API auth fallback
  4. SSL Verification Disabled - Mehrere Tools haben verify=False

Module-Übersicht

Core (core/)

  • orchestrator.py - ZenOrchestrator, Hauptkoordinator
  • plugin_manager.py - Plugin-System
  • rate_limiter.py - Rate Limiting
  • cache.py - Multi-Tier Caching
  • shield_integration.py - Zen Shield Integration

Agents (agents/)

  • react_agent.py - ReAct Pattern Implementierung
  • react_agent_enhanced.py - Erweiterter ReAct Agent
  • react_agent_vm.py - VM-basierter Agent
  • agent_orchestrator.py - Agent-Koordination
  • Spezialisierte Agents: research_agent, analysis_agent, exploit_agent

Autonomous (autonomous/)

  • agent_loop.py - State Machine (IDLE → PLANNING → EXECUTING → OBSERVING → REFLECTING → COMPLETED)
  • tool_executor.py - Tool-Ausführung mit Safety-Levels
  • exploit_validator.py - Sandbox-Validierung
  • memory.py - LangGraph Memory Integration
  • react.py - ReAct Core Loop

Risk Engine (risk_engine/)

  • false_positive_engine.py - Bayes'sche Filter + Multi-LLM Voting
  • business_impact_calculator.py - Finanzielle/Compliance-Auswirkungen
  • cvss.py - CVSS 3.1 Calculator
  • epss.py - EPSS Client

API (api/)

  • main.py - FastAPI App
  • auth.py - JWT Authentication
  • routes/ - 50+ API Endpunkte
  • websocket.py + websocket_v2.py - Real-time Updates

Tools (tools/)

  • Network: nmap_integration.py (fehlt!), masscan_integration.py, scapy_integration.py
  • Web: sqlmap_integration.py, gobuster_integration.py, burpsuite_integration.py
  • Exploit: metasploit_integration.py, hydra_integration.py
  • AD: bloodhound_integration.py, crackmapexec_integration.py, responder_integration.py

Memory (memory/)

  • 4-Layer Architecture: Working → Short-term → Long-term → Vector Store
  • Backends: SQLite, Redis
  • LangGraph Integration

CI/CD Workflows (58 total)

Kritische Workflows:

  • ci.yml - Haupt-CI
  • security.yml - Sicherheits-Scans
  • code-quality.yml - Linting & Formatting
  • pr-validation.yml - PR Checks
  • release.yml - Release-Prozess
  • deploy.yml - Deployment

Auto-Workflows:

  • dependabot-auto-merge.yml - Automatische Dependency-Updates
  • auto-fix-repository.yml - Automatische Fixes
  • health-check.yml - Repository-Health

Entwicklungs-Standards

Code Style

  • Black: Line length 127
  • isort: Profile "black"
  • Ruff: E, F, W rules
  • mypy: Type checking (optional)

Testing

  • pytest mit asyncio-Unterstützung
  • Coverage-Target: 70%
  • Security-Tests: Bandit, Safety

Security

  • Alle Dependencies auf CVE-Versionen prüfen
  • Keine Hardcoded Secrets
  • Input-Validierung mit input_validator.py
  • Zen Shield für Output-Sanitization

Wichtige Befehle

# Setup
pip install -e ".[dev]"

# Tests
pytest --cov=. --cov-report=html

# Linting
black .
isort .
flake8

# Security
bandit -r .
safety check

# API starten
uvicorn api.main:app --reload

# Docker
docker-compose up -d

Versions-Inkonsistenzen (zu fixen)

  • setup.py: Version 2.3.9 ✅
  • pyproject.toml: Version 2.3.9
  • README.md: Version 2.3.9 ✅
  • action.yml: Version 2.3.9

Empfohlene Version: 2.3.9

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.