Menu
Mandatory first-turn startup procedure — checks for existing engagements, resume/new selection, workspace initialization.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Red team engagement lifecycle management — initiation, phase transitions, go/no-go gates, deconfliction, emergency procedures, completion.
Final engagement report generation — executive summary, technical report, findings aggregation, attack path narrative, detection gap matrix, remediation roadmap.
Decepticon orchestrator patterns — delegation, state management, adaptive re-planning, context handoff protocols.
Use when setting up, running, or managing the Botron autonomous red team agent — Docker-based multi-provider LLM pentesting framework. Covers install, demo, service management, testing, and provider configuration.
Sliver C2 framework operations — server connection, listener setup, implant generation, BOF/Armory extensions, post-implant operations, HTTP C2 profiles.
Stage 1 broad-spectrum scanner playbook. Sharded sweep over very large codebases producing CANDIDATE nodes for the Detector to reason about. Load at scanner-agent startup.
| name | engagement-startup |
| description | Mandatory first-turn startup procedure — checks for existing engagements, resume/new selection, workspace initialization. |
| allowed-tools | Bash Read |
| metadata | {"subdomain":"orchestration","when_to_use":"agent startup, first message, session start","tags":"startup, engagement-selection, workspace-init, resume","mitre_attack":[]} |
Execute this procedure on every session start, before any other action.
bash(command="ls -1 /workspace/ 2>/dev/null || echo '[empty]'")
Present a numbered list and ask:
Existing engagements found:
1. acme-external-2026
2. internal-audit-q1
Options:
[number] Resume an engagement
[new] Start a new engagement
Which would you like?
No existing engagements found. Let's set up a new one.
What is the target or scope for this engagement?
read_file("<engagement>/plan/roe.json")
read_file("<engagement>/plan/conops.json")
read_file("<engagement>/plan/deconfliction.json")
read_file("<engagement>/plan/opplan.json")
read_file("<engagement>/findings.md")
Soundwave has already interviewed the operator and created the engagement documents (RoE, CONOPS, Deconfliction Plan) before the orchestrator was activated. The workspace and planning documents already exist.
bash(command="ls /workspace/plan/roe.json /workspace/plan/conops.json /workspace/plan/deconfliction.json")
soundwave to regenerate:
task("soundwave", "Engagement workspace: /workspace/. Regenerate missing planning documents.")
bash(command="nc -z c2-sliver 31337 2>/dev/null && echo 'C2_REACHABLE' || echo 'C2_UNREACHABLE'")
C2_REACHABLE → C2 framework is Sliver (server: c2-sliver, gRPC port 31337). Include this in ALL sub-agent delegations.C2_UNREACHABLE → C2 server is not available, skip C2-dependent objectives