jonastbrg

Run sustained security assessment campaigns against targets using the Ralph Wiggum autonomous loop pattern. Use when asked to start, continue, or manage a pentest campaign.

Control a Flipper Zero and scan BLE targets for authorized security research. Use when asked to interact with Flipper hardware, scan BLE devices, or control RF/IR/NFC/RFID.

Start an autonomous pentest loop. Spawns fresh-context subagents for each phase. Use: /ralph-loop

BLE GATT exploitation methodology — scanning, enumeration, characteristic analysis, payload crafting, and write attacks against Bluetooth Low Energy devices

Run a sustained security assessment campaign — a real pentest, not a simulation

Credential testing methodology — default credential checking, password spraying, credential reuse, and OSINT for leaked credentials

Test default credentials against network services — SSH, HTTP, FTP, Telnet, MQTT, MySQL, PostgreSQL, Redis, MongoDB

Control ESP32 Marauder via serial — WiFi scanning, deauth, beacon spam, probe flood, raw commands

Analyze and visualize BLOOM evaluation results across probes, models, and conditions. Use: /bloom-analyze [--probe <name>] [--model <name>]

Run a full BLOOM behavioral evaluation pipeline for a probe. Orchestrates all 4 stages. Use: /bloom-eval <probe_name>

Stage 2 only: generate diverse trigger scenarios for a probe. Use: /bloom-ideate <probe_name> [--n N]

Stage 4 only: score all traces for a probe and write judgment.json files. Use: /bloom-judge <probe_name>

Stage 3 only: run all trials for a probe (spawns parallel subagents). Use: /bloom-rollout <probe_name>

Run BLOOM evaluations at scale across multiple probes, models, and repetitions. Use: /bloom-sweep --probe <name> --models <m1,m2> --scenarios N --reps N [--setup] [--parallel]

Stage 1 only: deeply analyze a behavioral probe and write understanding.json. Use: /bloom-understand <probe_name>