engagement-startup
Mandatory first-turn startup procedure — checks for existing engagements, resume/new selection, workspace initialization.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-09
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- engagement-startup
- metadata
- { "tags": "startup, engagement-selection, workspace-init, resume", "subdomain": "orchestration", "when_to_use": "agent startup, first message, session start", "upstream_ref": "Decepticon orchestrator first-turn bootstrap — workspace + engagement selection, no direct attack technique" }
- description
- Mandatory first-turn startup procedure — checks for existing engagements, resume/new selection, workspace initialization.
- allowed-tools
- Bash Read
03 SKILL.md 正文
Engagement Startup Procedure
Execute this procedure on every session start, before any other action.
Step 1: Discover Existing Engagements
bash(command="ls -1 /workspace/ 2>/dev/null || echo '[empty]'", description="List existing engagement workspaces")
Step 2: Present Options to Operator
If engagements exist
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?
If no engagements exist
No existing engagements found. Let's set up a new one.
What is the target or scope for this engagement?
Step 3A: Resume Existing Engagement
- Read planning documents:
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 relevant files under "<engagement>/findings/" - Summarize progress to the operator:
- Objectives completed / total
- Current phase (recon / exploit / post-exploit)
- Last completed objective and key findings
- Next pending objective
- Ask: "Continue from where we left off?"
- Begin the Ralph execution loop
Step 3B: New Engagement (docs already created by Soundwave)
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.
- Verify documents exist:
If any are missing, delegate tobash(command="ls plan/roe.json plan/conops.json plan/deconfliction.json", description="Verify the planning documents exist")soundwaveto regenerate:task("soundwave", "Engagement workspace: /workspace/. Regenerate missing planning documents.") - Check C2 Infrastructure:
bash(command="nc -z c2-sliver 31337 2>/dev/null && echo 'C2_REACHABLE' || echo 'C2_UNREACHABLE'", description="Check whether the C2 server is reachable")- If
C2_REACHABLE→ C2 framework is Sliver (server:c2-sliver, gRPC port 31337). Include this in ALL sub-agent delegations. - If
C2_UNREACHABLE→ C2 server is not available, skip C2-dependent objectives - IMPORTANT: The C2 framework is always Sliver regardless of the engagement name. Do NOT assume Metasploit from engagement names containing "msf".
- If
- Begin the Ralph execution loop (Phase 1: read CONOPS → build OPPLAN)
04 同仓库更多 Skills
wps-pixie-dust
WPS Pixie-Dust offline nonce attack (reaver -K / pixiewps) and fallback online PIN brute (bully) to recover the AP's WPA PSK without capturing a handshake.
wpa3-sae
WPA3-SAE transition-mode downgrade (DragonShift), SSID Confusion CVE-2023-52424, Dragonblood side-channels, and SAE captive-portal credential recovery against WPA3-Personal networks.
wpa2-psk
WPA/WPA2-PSK handshake capture via targeted deauth + PMKID (no deauth required) + offline hashcat cracking. The most common consumer/SMB encryption mode in 2026.
wpa-enterprise-eap
WPA/WPA2/WPA3-Enterprise (802.1X/EAP) rogue-RADIUS evil-twin for MSCHAPv2 capture, GTC downgrade, and PEAP relay. MSCHAPv2 capture equals a NetNTLM hash — the primary wireless on-ramp to Active Directory.
krack-fragattacks
KRACK key-reinstallation (CVE-2017-13077..13082) and FragAttacks fragmentation/aggregation flaws (CVE-2020-24586..24588, CVE-2020-26139..26147) against legacy or embedded 802.11 supplicants with poor patch cadence.
evil-twin-karma
Evil-twin rogue AP with KARMA/Mana PNL-probe response, captive-portal credential capture, and post-association MITM for PSK/open networks. Distinct from wpa-enterprise-eap which targets 802.1X.