Skip to content
BreachPilot

Multi-agent orchestration

The six-agent swarm

Six specialists share one blackboard with a battle log: parallel dispatch, phase-aware skill hints and cross-phase negotiation — supervised, target-locked, and fully audited.

The specialists

Six agents, one shared mission

Each agent owns a phase of the assessment. They read and write shared state instead of passing messages in a chain — for authorized targets only.

  • recon

    Recon

    Attack-surface discovery and fingerprinting

    Scanning, fingerprinting and attack-surface scoring. Opens the run and keeps the target model fresh as new services appear.

  • vuln

    Vuln

    Vulnerability / CVE and module correlation

    CVE and exploit correlation plus module matching — pairs threat intel (NVD, EPSS, KEV) with applicable capabilities.

  • exploit

    Exploit

    Capability selection, payload work and execution

    Module selection, payload crafting and mutation, execution through the MCP tool layer under policy and allowlist.

  • post_exploit

    Post Exploit

    Credential, loot and lateral-target handling

    Credential and loot handling, lateral-target generation — still inside the same target lock.

  • critic

    Critic

    Scope, risk and policy review

    Pre-execution scope, risk and policy review. The conscience of the swarm: forbidden actions and disallowed assets die here.

  • reflection

    Reflection

    Strategy review and lessons

    Strategy review and lessons learned — feeds the experience store so the next run starts smarter.

Shared state

Blackboard + battle log

Agents don't pass messages in a chain — they read and write shared state. The blackboard holds the target model, hypotheses, findings and plan; the battle log records who decided what, so runs stay debuggable and resumable.

Single-target swarm mode

--swarm decomposes one authorized target across the six specialists: parallel recon plus vuln research, critic pre-check, reflection shifts. Best for going deep on a high-value system you own or have written permission to test.

Persistent campaign orchestration

Without --swarm, the autonomous campaign drives a persistent multi-phase queue — recon → exploit → privesc → lateral → validation — with adaptive aggression, resume and checkpoints across one or many authorized targets. Same target-IP lock and permission model either way.

Authorized testing only — the swarm runs against allowlisted targets under the mission scope gate, with every decision in a tamper-evident audit chain. Only test systems you own or have explicit written permission to assess. Safety model