offensive-tools/wireless/sparrow-wifi/SKILL.md
Linux Wi‑Fi and Bluetooth analyzer with GPS, remote agent, JSON API, and SDR integrations including HackRF One and Ubertooth. Use when you need combined Wi‑Fi/Bluetooth situational awareness, remote wireless sensors, spectrum overlays, Bluetooth visibility, or HackRF-assisted spectrum workflows beyond simple CLI capture.
npx skillsauth add aeondave/malskill sparrow-wifiInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Integrated Wi‑Fi / Bluetooth / SDR analysis platform for Linux with optional remote agent and HackRF/Ubertooth workflows.
Choose Sparrow when you need one platform for:
# install deps (common Linux/Kali/Debian path)
git clone https://github.com/ghostop14/sparrow-wifi
cd sparrow-wifi
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt
# run desktop app
sudo venv/bin/python3 ./sparrow-wifi.py
| Component | Use |
|---|---|
| sparrow-wifi.py | Desktop GUI for Wi‑Fi/BT/spectrum awareness |
| sparrowwifiagent.py | Headless HTTP agent for remote sensors |
| sparrow-droneid | Drone RemoteID Wi‑Fi/BLE detection workflow |
| sparrow-elastic.py | Optional Elasticsearch / OpenSearch bridge |
sudo ./sparrowwifiagent.py
# default API port 8020
Example API calls:
curl http://sensor:8020/wireless/interfaces
curl http://sensor:8020/wireless/networks/wlan0
curl http://sensor:8020/bluetooth/discoverystarta
curl http://sensor:8020/bluetooth/discoverystatus
Sparrow fills the gap not covered by the current category:
| Skill | Best use |
|---|---|
| kismet | Passive WIDS / long-running passive RF logging |
| aircrack-ng | Focused Linux monitor-mode capture and cracking workflows |
| bluez | Core Bluetooth CLI operations |
| sparrow-wifi | Combined Wi‑Fi/Bluetooth/SDR awareness with APIs and sensors |
| File | When to load |
|---|---|
| references/hackrf-bluetooth-agent-workflows.md | For HackRF One, Bluetooth, remote agent, API, and hardware-selection workflows |
data-ai
Scoped routing: Linux operator; hosts, sessions, users, services, packages, logs, containers, SSH, network paths, privilege evidence.
development
Offensive methodology for ICS/OT/SCADA environments in authorized industrial penetration testing and red team operations. Use when assessing PLCs, RTUs, HMIs, engineering workstations, historians, or field devices running Modbus, DNP3, EtherNet/IP, S7comm/S7+, Profinet, IEC 60870-5-104, BACnet, or OPC-UA. Covers passive OT network enumeration, protocol-level device interrogation, PLC coil/register read-write attacks, HMI session exploitation, historian and engineering workstation compromise, and safe escalation rules for critical infrastructure scope. Does not cover: general IT network exploitation (network-technique), physical hardware interfaces UART/JTAG/SPI (hardware-technique), wireless sensor network attacks (wireless-technique), RF/SDR signal analysis (hardware-ctf or wireless-technique), or CTF-framed ICS lab tasks (ics-ctf).
tools
Offensive methodology for authorized game security assessments, game client security research, and game-adjacent penetration testing in real-world engagements. Use when assessing game clients for cheating vulnerabilities, testing anti-cheat effectiveness, auditing game server protocols for score manipulation or economic fraud, reverse engineering game DRM or license validation, analyzing game save file protection, or assessing game mod/plugin security. Covers: process memory scanning and manipulation (Cheat Engine methodology), game binary reversing for license and DRM bypass, game network protocol analysis and packet replay, anti-cheat mechanism analysis, save file format reversing and tampering, speed hack and value injection techniques. Does NOT cover: CTF game challenges (game-ctf), game engine source code auditing (web-exploit-technique or vuln-search-technique for the backend), or general binary exploitation (pwn-ctf or reversing-technique).
development
Auth assessment: hardware/embedded methodology; UART/JTAG/SWD/SPI/I2C, firmware extraction, boot/debug paths, embedded OS evidence.