agentleFS
SHAdd0WTAkaSHAdd0WTAka/Zen-Ai-Pentest/.agents/skills/poc-validator/SKILL.md

poc-validator

Skill470 starsChanged 4 months agoMITView on GitHub

Proof-of-Concept (PoC) Validation Skill for security exploit verification. Use when validating exploitability of vulnerabilities, generating tailored payloads, executing exploits in sandboxed environments, or verifying successful exploitation (e.g., SQL injection, CVE exploitation, command injection). Triggers on tasks involving payload generation, exploit execution verification, sandboxed testing, or confirmation of administrative access/data exfiltration after exploitation attempts.

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use scripts/sandbox_executor.py for isolated exploit testing:

    line 54
  2. Distinctive:

    Read-only filesystem with tmpfs for output

    line 58
  3. Distinctive:

    Critical: All exploit execution MUST use sandbox.

    line 61
  4. Very specific:

    Use scripts/verify_exploit.py to confirm exploitation:

    line 65
  5. Distinctive:

    RCE: Verify command output in response

    line 67
  6. Distinctive:

    File Upload: Verify file presence/execution

    line 70
  7. Distinctive:

    Before any exploit execution:

    line 103

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

PoC-Validator Skill

Validates vulnerability exploitability through controlled payload generation, sandboxed execution, and success verification.

Quick Start

Generate and validate a PoC for SQL injection:

from scripts.payload_generator import PayloadGenerator
from scripts.sandbox_executor import SandboxExecutor
from scripts.verify_exploit import ExploitVerifier

# Generate payload
gen = PayloadGenerator()
payload = gen.generate_sql_payload(
    target_url="http://target.com/login",
    parameter="username",
    technique="error_based"
)

# Execute in sandbox
executor = SandboxExecutor()
result = await executor.execute_sqlmap(
    target="http://target.com/login",
    payload=payload,
    risk_level=2
)

# Verify success
verifier = ExploitVerifier()
is_exploitable = await verifier.verify_sql_injection(result)

Workflow

1. Payload Generation

Use scripts/payload_generator.py for:

  • CVE-based exploits: Lookup known payloads from vulnerability_mapping.json
  • SQL Injection: Error-based, Union-based, Time-based, Boolean-based
  • Command Injection: System command payloads with evasion techniques
  • Path Traversal: Directory traversal sequences
  • XXE/XML Injection: External entity payloads

See references/payload_patterns.md for complete payload library.

2. Sandbox Execution

Use scripts/sandbox_executor.py for isolated exploit testing:

  • Docker container isolation with resource limits
  • Network isolation (no egress to private ranges)
  • Execution timeouts (default: 300s)
  • Read-only filesystem with tmpfs for output
  • Automatic cleanup post-execution

Critical: All exploit execution MUST use sandbox. Never run exploits directly on host.

3. Success Verification

Use scripts/verify_exploit.py to confirm exploitation:

  • SQL Injection: Detect database version extraction, table enumeration
  • RCE: Verify command output in response
  • Auth Bypass: Confirm session token/admin access
  • Data Exfiltration: Detect sensitive data patterns in responses
  • File Upload: Verify file presence/execution

Risk Levels

LevelPayload TypeToolsUse Case
0Passive detectionNoneVulnerability confirmation only
1Safe payloadsSQLMap --risk 1Non-destructive testing
2Active exploitationSQLMap --risk 2, MetasploitControlled exploitation
3AggressiveAll tools with full payloadsFull PoC validation

Integration with Zen-AI-Pentest

# Integration with ExploitAgent
from autonomous.exploit_validator import ExploitValidator

def validate_poc(self, vulnerability: dict) -> dict:
    """Validate vulnerability with PoC execution."""
    validator = ExploitValidator(
        sandbox_enabled=True,
        risk_level=vulnerability.get("risk", 1)
    )

    return validator.validate(
        vuln_type=vulnerability["type"],
        target=vulnerability["target"],
        evidence=vulnerability["evidence"]
    )

Safety Controls

Before any exploit execution:

  1. Validate target is not in private ranges (guardrails/ip_validator.py)
  2. Confirm explicit authorization in database
  3. Set execution timeout
  4. Enable Docker sandbox
  5. Log all actions to audit trail

See references/safety_requirements.md for complete safety checklist.

Error Handling

ErrorCauseSolution
Sandbox timeoutPayload too slowIncrease timeout or use faster technique
Container crashResource exhaustionReduce threads, increase memory limit
Network blockedEgress filteringVerify allowed outbound in config
Verification failedWAF/IPS blockingTry evasion techniques from payload_patterns.md

Output Format

{
  "poc_id": "uuid",
  "vulnerability_id": "vuln-123",
  "status": "verified|failed|inconclusive",
  "exploit_type": "sql_injection|rce|xxe|...",
  "payload_used": "...",
  "sandbox_logs": "...",
  "evidence": {
    "before": "...",
    "after": "...",
    "extracted_data": "..."
  },
  "risk_level": 2,
  "timestamp": "2026-03-20T14:46:00Z",
  "verified_by": "exploit_agent_v3"
}

References

  • Payload Patterns Library - Complete payload collection
  • Sandbox Setup Guide - Docker configuration details
  • Safety Requirements - Mandatory safety checks
  • CVE Database Schema - CVE lookup structure

Scripts

  • scripts/payload_generator.py - Generate tailored exploit payloads
  • scripts/sandbox_executor.py - Execute exploits in Docker sandbox
  • scripts/verify_exploit.py - Verify exploitation success
  • scripts/cleanup_sandbox.py - Clean up sandbox resources

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.