/operator
Overview
The /operator command starts an interactive operator session where you work alongside the AI agent in real time. Unlike /pentest which runs autonomously, operator mode gives you step-by-step control over the testing process — you can approve actions, steer the agent’s focus, and intervene at any point.
Usage
With flags:
Alias: /o
How It Works
Operator Modes
Manual mode is the default and recommended for learning or when testing
sensitive targets. Auto mode is closer to /pentest but keeps you in the
loop with the ability to pause and redirect.
Command Flags
When to Use /operator vs /pentest
Autonomous mode — set a target and let the AI agent swarm run independently. Best for comprehensive, hands-off testing.
Interactive mode — guide the AI agent step by step. Best for targeted investigations, learning, or sensitive environments.
Example Workflow
Operator Skills
You can extend operator mode with custom skills using /create-skill. Skills are reusable instruction sets that teach the agent specialized testing techniques or workflows for your specific environment.
Best Practices
Tips for Operator Mode: 1. Start with plan mode to review the agent’s testing strategy before execution 2. Use manual mode for sensitive targets where you want full control 3. Switch to auto mode once you’re comfortable with the agent’s approach 4. Create skills for repetitive testing patterns in your environment
Security Reminder: Only test systems you own or have explicit authorization to test. Unauthorized testing is illegal.
After Starting
Once you start an operator session:
- The AI agent begins analysis based on your chosen mode
- You interact in real time, approving or steering actions
- Findings are reported as they’re discovered
- The session is automatically saved and can be resumed via
/sessions