offensive-tools/api/kiterunner/SKILL.md
Context-aware API route discovery and brute-forcing using real-world API schema wordlists. Use when enumerating API endpoints, discovering hidden routes on REST/gRPC services, or replacing dirbusting for API surfaces.
npx skillsauth add aeondave/malskill kiterunnerInstall 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.
Context-aware API route brute-forcer using real-world API schema wordlists (Assetnote).
# Download binary from https://github.com/assetnote/kiterunner/releases
# Scan with default wordlist
kr scan https://target.com -w routes-small.kite
# Scan from file of hosts
kr scan hosts.txt -w routes-large.kite -x 20
# Replay a finding with full request detail
kr replay -w routes-small.kite "GET 403 [ 191, 9, 1] https://target.com/api/v1/user"
| Flag | Purpose |
|------|---------|
| -w FILE | Kite wordlist (.kite or .txt) |
| -x N | Concurrent requests |
| --ignore-length N | Filter by response length |
| -H "K:V" | Custom header |
| -A "bearer:TOKEN" | Auth header shorthand |
| --fail-status-codes | Codes treated as failures |
| --success-status-codes | Codes treated as hits |
| -o json | JSON output |
| --delay N | Per-request delay (ms) |
Authenticated API scan:
kr scan https://api.target.com -w routes-large.kite -A "bearer:$TOKEN" -x 30
Filter noise — ignore typical 404/400 lengths:
kr scan https://api.target.com -w routes-small.kite --ignore-length 19
Replay to inspect full response:
kr replay -w routes-large.kite "POST 200 [ 512, 10, 2] https://api.target.com/api/v2/admin"
| File | When to load |
|------|--------------|
| references/ | Wordlist sources and API fingerprinting notes |
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.