What makes Pilot Penetration Testing Setup notable?

964 downloads. Trust evidence available

How should Pilot Penetration Testing Setup be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Pilot Penetration Testing Setup

Deploy an automated penetration testing pipeline with 4 agents. Use this skill when: 1. User wants to set up a penetration testing or security assessment pip... Skill: Pilot Penetration Testing Setup Owner: teoslayer Summary: Deploy an automated penetration testing pipeline with 4 agents. Use this skill when: 1. User wants to set up a penetration testing or security assessment pip... Tags: latest:1.0.0 Version history: v1.0.0 | 2026-04-23T03:40:33.457Z | user Initial release Archive index: Archive v1.0.0: 4 files, 6184 bytes Files: README.md (5054b), skill-card.md (2383b), S

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

964

Updated

Oct 12, 2026

Version

1.0.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 964 downloads reported by the source. Last updated 10/12/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 12, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 12, 2026
Adoption signal: 964 downloadsadoption · observed Oct 12, 2026
Latest release: 1.0.0release · observed Apr 23, 2026
Handshake status: UNKNOWNsecurity

What changed

Newest first. Only changes that point at a source are listed.

Release 1.0.0release
Initial release
Observed Apr 23, 2026 · source

Install and run

Setup complexity: low.

clawhub skill install s1774mw0xjm94md84a5rvrp9rd84fear:pilot-penetration-testing-setup

Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-teoslayer-pilot-penetration-testing-setup/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

16,646 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: pilot-penetration-testing-setup
description: >
  Deploy an automated penetration testing pipeline with 4 agents.

  Use this skill when:
  1. User wants to set up a penetration testing or security assessment pipeline
  2. User is configuring an agent as part of a vulnerability scanning workflow
  3. User asks about recon, vulnerability scanning, exploit validation, or pentest reporting across agents

  Do NOT use this skill when:
  - User wants to run a single vulnerability scan (use pilot-task-parallel instead)
  - User wants to send a one-off security alert (use pilot-webhook-bridge instead)
tags:
  - pilot-protocol
  - setup
  - security
  - pentest
license: AGPL-3.0
metadata:
  author: vulture-labs
  version: "1.0"
  openclaw:
    requires:
      bins:
        - pilotctl
        - clawhub
    homepage: https://pilotprotocol.network
allowed-tools:
  - Bash
---

# Penetration Testing Setup

Deploy 4 agents that perform recon, scan vulnerabilities, validate exploits, and generate reports.

## Roles

| Role | Hostname | Skills | Purpose |
|------|----------|--------|---------|
| recon | `<prefix>-recon` | pilot-discover, pilot-stream-data, pilot-archive | DNS enumeration, port scanning, service fingerprinting |
| scanner | `<prefix>-scanner` | pilot-task-parallel, pilot-metrics, pilot-dataset | Vulnerability scans, CVE checks, misconfiguration detection |
| exploiter | `<prefix>-exploiter` | pilot-task-chain, pilot-audit-log, pilot-receipt | Safe proof-of-concept validation, exploitability confirmation |
| reporter | `<prefix>-reporter` | pilot-webhook-bridge, pilot-share, pilot-slack-bridge | Report generation with findings, risk ratings, remediation |

## Setup Procedure

**Step 1:** Ask the user which role this agent should play and what prefix to use.

**Step 2:** Install the skills for the chosen role:
```bash
# For recon:
clawhub install pilot-discover pilot-stream-data pilot-archive
# For scanner:
clawhub install pilot-task-parallel pilot-metrics pilot-dataset
# For exploiter:
clawhub install pilot-task-chain pilot-audit-log pilot-receipt
# For reporter:
clawhub install pilot-webhook-bridge pilot-share pilot-slack-bridge
```

**Step 3:** Set the hostname:
```bash
pilotctl --json set-hostname <prefix>-<role>
```

**Step 4:** Write the setup manifest:
```bash
mkdir -p ~/.pilot/setups
cat > ~/.pilot/setups/penetration-testing.json << 'MANIFEST'
<INSERT ROLE MANIFEST FROM BELOW>
MANIFEST
```

**Step 5:** Tell the user to initiate handshakes with direct communication peers.

## Manifest Templates Per Role

### recon
```json
{
  "setup": "penetration-testing", "setup_name": "Penetration Testing",
  "role": "recon", "role_name": "Reconnaissance Agent",
  "hostname": "<prefix>-recon",
  "description": "Performs passive and active reconnaissance — DNS enumeration, port scanning, service fingerprinting.",
  "skills": {
    "pilot-discover": "Enumerate DNS records, subdomains, and service endpoints.",
    "pilot-stream-data": "Stream port s

README.md

# Penetration Testing

Deploy an automated penetration testing pipeline with 4 agents that perform reconnaissance, scan for vulnerabilities, validate exploitability with safe proof-of-concept tests, and generate comprehensive pentest reports. Each agent handles a stage of the assessment -- recon, scanning, validation, and reporting -- so security assessments are methodical, thorough, and well-documented.

**Difficulty:** Advanced | **Agents:** 4

## Roles

### recon (Reconnaissance Agent)
Performs passive and active reconnaissance -- DNS enumeration, port scanning, service fingerprinting. Builds a target profile with attack surface mapping.

**Skills:** pilot-discover, pilot-stream-data, pilot-archive

### scanner (Vulnerability Scanner)
Runs automated vulnerability scans, checks CVE databases, identifies misconfigurations. Prioritizes findings by CVSS score and exploitability.

**Skills:** pilot-task-parallel, pilot-metrics, pilot-dataset

### exploiter (Exploit Validator)
Validates discovered vulnerabilities with safe proof-of-concept tests, confirms exploitability. Documents evidence and impact without causing damage.

**Skills:** pilot-task-chain, pilot-audit-log, pilot-receipt

### reporter (Pentest Reporter)
Generates penetration test reports with findings, risk ratings, remediation steps, and executive summary. Delivers to stakeholders via Slack and webhooks.

**Skills:** pilot-webhook-bridge, pilot-share, pilot-slack-bridge

## Data Flow

```
recon    --> scanner  : Recon results with target profile and services (port 1002)
scanner  --> exploiter: Vulnerability findings with CVE and severity (port 1002)
exploiter--> reporter : Validated findings with proof-of-concept evidence (port 1002)
reporter --> external : Pentest report via webhook and Slack (port 443)
```

## Setup

Replace `<your-prefix>` with a unique name for your deployment (e.g. `acme`).

### 1. Install skills on each server

```bash
# On server 1 (reconnaissance agent)
clawhub install pilot-discover pilot-stream-data pilot-archive
pilotctl set-hostname <your-prefix>-recon

# On server 2 (vulnerability scanner)
clawhub install pilot-task-parallel pilot-metrics pilot-dataset
pilotctl set-hostname <your-prefix>-scanner

# On server 3 (exploit validator)
clawhub install pilot-task-chain pilot-audit-log pilot-receipt
pilotctl set-hostname <your-prefix>-exploiter

# On server 4 (pentest reporter)
clawhub install pilot-webhook-bridge pilot-share pilot-slack-bridge
pilotctl set-hostname <your-prefix>-reporter
```

### 2. Establish trust

Agents are private by default. Each pair that communicates must exchange handshakes. When both sides send a handshake, trust is auto-approved -- no manual step needed.

```bash
# On recon:
pilotctl handshake <your-prefix>-scanner "setup: penetration-testing"
# On scanner:
pilotctl handshake <your-prefix>-recon "setup: penetration-testing"
# On scanner:
pilotctl handshake <your-prefix>-exploiter "setup: penetration-testing"
# On exploiter:
pilotctl ha

_meta.json

{
  "ownerId": "kn7b7ecgny18169gnmmnxx76ns80py0g",
  "slug": "pilot-penetration-testing-setup",
  "version": "1.0.0",
  "publishedAt": 1776915633457
}

skill-card.md

## Description:

Deploy an automated penetration testing pipeline with 4 agents.

This skill is ready for commercial/non-commercial use.

## Publisher:

[teoslayer](https://clawhub.ai/user/teoslayer)

### License/Terms of Use:

MIT-0

## Use Case:

Security engineers and developers use this skill to configure a four-agent penetration testing workflow for authorized reconnaissance, vulnerability scanning, exploit validation, and reporting.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The setup is intended for penetration testing and could be misused outside an authorized assessment.

Mitigation: Use it only for approved security assessments with defined targets, scope, and authorization.

Risk: The setup installs dependency skills without pinned versions.

Mitigation: Pin and verify dependency skills before installation.

Risk: Prefix and role placeholders can lead to unsafe or unintended shell and hostname values.

Mitigation: Restrict prefix and role values to reviewed, known-safe names before running setup commands.

Risk: Reports may contain sensitive penetration test findings and can be sent to Slack or webhook destinations.

Mitigation: Review report content and send it only to approved Slack or webhook destinations.

Risk: Peer handshakes can establish trust between the wrong agents if identities are not checked.

Mitigation: Verify peer identities before handshakes and remove ~/.pilot/setups/penetration-testing.json when the deployment is no longer needed.

## Reference(s):

- [ClawHub skill page](https://clawhub.ai/teoslayer/skills/pilot-penetration-testing-setup)
- [Pilot Protocol homepage](https://pilotprotocol.network)

## Skill Output:

**Output Type(s):** [Guidance, Shell commands, Configuration, Markdown]

**Output Format:** [Markdown with inline shell commands and JSON configuration templates]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Produces role-specific setup steps for a four-agent pipeline and a local penetration-testing manifest.]

## Skill Version(s):

1.0.0 (source: server release metadata)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 3d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.

MCPOPENCLAW

Github ReposUpdated 7mo agoRank 70

CopilotKit

The Frontend for Agents & Generative UI. React + Angular