Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 40321–40350 of 43431 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| web-sql-injection-unionajtazer/heckitYou are helping a penetration tester exploit UNION-based SQL injection. The | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| web-ssrfajtazer/heckitYou are helping a penetration tester exploit server-side request forgery. The | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| web-ssti-freemarkerajtazer/heckitYou are helping a penetration tester exploit server-side template injection in a | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| web-ssti-jinja2ajtazer/heckitYou are helping a penetration tester exploit server-side template injection in a | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| web-ssti-twigajtazer/heckitYou are helping a penetration tester exploit server-side template injection in a | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| web-tomcat-manager-deployajtazer/heckitYou are helping a penetration tester exploit authenticated access to Apache | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| web-web-discoveryajtazer/heckitYou are helping a penetration tester discover vulnerabilities in a web | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| web-xss-domajtazer/heckitYou are helping a penetration tester exploit DOM-based cross-site scripting. The | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| web-xss-reflectedajtazer/heckitYou are helping a penetration tester exploit reflected cross-site scripting. The | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| web-xss-storedajtazer/heckitYou are helping a penetration tester exploit stored (persistent) cross-site | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| web-xxeajtazer/heckitYou are helping a penetration tester exploit XXE injection. The target application | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| offensive-bluetooth-bleajtazer/heckitBluetooth Low Energy (BLE) attack methodology — GATT enumeration, characteristic read/write without auth, pairing downgrade (Just Works forced), LE Secure Connections bypass, MITM via active relay, sniffing with Sniffle (TI CC1352) / Ubertooth / Frontline, encryption key extraction (LE Legacy Pairing crackable, LE Secure Connections strong), proximity authentication abuse (cars, locks), and companion-app trust analysis. Use for IoT BLE devices, smart locks, fitness trackers, medical devices, BLE beacons, or any device pairing over BLE. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| offensive-bluetooth-classicajtazer/heckitBluetooth Classic (BR/EDR) attack methodology — device discovery, service enumeration via SDP, LMP/L2CAP layer attacks, legacy PIN cracking (BlueBorne / KNOB), Bluetooth file-transfer abuse (BlueSnarfing legacy), unauthenticated profile abuse (HSP, HFP, OPP), and modern relevance against older industrial / automotive / accessory targets. Use when in-scope devices use Bluetooth Classic (Bluetooth ≤ 4.0 BR/EDR) — common in legacy car kits, industrial sensors, older medical devices, and audio accessories. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| offensive-deauth-disassocajtazer/heckitDeauthentication and disassociation attacks against 802.11 networks — targeted single-client deauth for handshake capture, broadcast deauth for DoS (with authorization), action-frame attacks bypassing 802.11w (PMF), beacon flooding, mdk4 / aireplay-ng tooling, and rate-limit / PMF-aware operation. Use to coerce client reconnection (handshake capture, evil-twin roaming), as targeted DoS, or to test PMF posture. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| offensive-evil-twinajtazer/heckitEvil Twin / KARMA / Mana access point methodology — rogue AP construction with hostapd-mana / wifiphisher / airgeddon, KARMA universal probe response, Mana selective probe response, captive portal phishing, deauth-driven client coercion to attacker AP, MAC randomization defeat via PNL leak analysis, post-association MITM (DNS, ARP, transparent proxy), credential capture for portal/web/SMB, and detection-evasion tactics. Use to coerce client devices onto an attacker-controlled AP, intercept their traffic, harvest credentials, or deliver payloads via captive portal. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| offensive-iotajtazer/heckitIoT and embedded device security testing methodology. Covers hardware reconnaissance (UART, JTAG, SWD, SPI flash, I2C EEPROM, eMMC chip-off), firmware acquisition (vendor portals, OTA capture, flash dump, binwalk extraction), firmware analysis (filesystem mounting, binary triage, hardcoded secrets, default credential discovery), bootloader attacks (U-Boot console, secure-boot bypass, fault injection), runtime attacks on embedded Linux/RTOS (busybox CVEs, MTD writes, /dev/mem), wireless protocol attacks (Zigbee, BLE, Z-Wave, LoRaWAN, Thread/Matter, sub-GHz), MQTT/CoAP/Modbus/BACnet/OPC-UA exploitation, mobile companion app analysis, cloud-IoT API abuse, and side-channel/glitching basics. Use for IoT pentest, smart-home assessment, ICS/OT testing, or embedded vulnerability research. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| offensive-krack-fragattacksajtazer/heckitKRACK (CVE-2017-13077..082) and FragAttacks (CVE-2020-24586..588 + 26139-26147) — key reinstallation, fragmentation, and aggregation attacks against WPA2 supplicants. Covers Vanhoef's test scripts, viability against modern patched stacks (mostly mitigated post-2021), residual unpatched embedded devices and IoT vendors, and the practical limitations of these attacks in modern engagements. Use when assessing legacy supplicants, embedded clients, or vendors with poor patch cadence. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| offensive-lorawan-sub-ghzajtazer/heckitLoRaWAN and sub-GHz (433 / 868 / 915 MHz) attack methodology — LoRaWAN ABP/OTAA join attack, network/session key reuse, frame counter replay, downlink injection on TTN/Helium-style networks, sub-GHz protocol replay (KeeLoq garage doors, fixed-code remotes, TPMS spoofing, smart plug telemetry), HackRF / RTL-SDR / Flipper Zero workflows, signal analysis with Inspectrum / Universal Radio Hacker, and reconstruction of proprietary packet formats. Use for LoRaWAN deployments (smart cities, asset tracking, industrial telemetry), or any wireless device using the unlicensed 433/868/915 MHz bands (garage openers, doorbells, IoT sensors, RC equipment). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| offensive-wifiajtazer/heckitWireless / 802.11 attack methodology for red team engagements and wireless security assessments. Covers monitor-mode setup, WPA/WPA2-PSK handshake capture and PMKID attacks, WPA3 SAE downgrade and Dragonblood, WPA-Enterprise (EAP) attacks (MSCHAPv2 cracking, EAP-TLS cert theft, evil-twin RADIUS), Karma / Known Beacons / Mana evil twin attacks, captive-portal phishing, KRACK and FragAttacks, WPS Pixie Dust, deauthentication and disassociation attacks, rogue AP construction (hostapd-mana), 802.1X bypass, MAC randomization defeat, BLE/Zigbee/IEEE 802.15.4 sidebands, and Wi-Fi 6/6E/7 considerations. Use when scoping wireless pentest, war-driving an estate, or testing corporate wireless segmentation. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| offensive-wifi-reconajtazer/heckitWi-Fi reconnaissance methodology — adapter selection, monitor mode and packet injection setup, regulatory domain handling, multi-band airspace mapping, hidden SSID discovery, BSSID/ESSID/channel/PMF/encryption fingerprinting, client probe analysis, vendor OUI lookup, war-driving with Kismet/airodump-ng/Wigle, and structured airspace data capture for downstream attacks. Use at the start of any wireless engagement to build the target map before active attacks; covers 2.4 GHz, 5 GHz, and 6 GHz (Wi-Fi 6E) bands and adapter compatibility for each. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| offensive-wpa-enterpriseajtazer/heckitWPA/WPA2/WPA3-Enterprise (802.1X / EAP) attack methodology — EAP method identification (PEAP-MSCHAPv2, EAP-TTLS, EAP-TLS, EAP-GTC, EAP-PWD, EAP-FAST), evil-twin RADIUS attacks with eaphammer for credential capture, MSCHAPv2 challenge-response cracking, EAP-TLS client certificate theft paths (DPAPI, NDES, AD CS auto-enrollment), supplicant validation bypass (missing server cert validation, missing CN pinning, BYOD misconfigurations), and post-capture pivots into AD via cracked domain credentials. Use for corporate Wi-Fi engagements where the network is 802.1X authenticated. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| offensive-wpa2-pskajtazer/heckitWPA/WPA2-PSK attack methodology — four-way handshake capture via targeted deauthentication, PMKID attacks (no client required), hcxdumptool / hcxpcapngtool conversion to hashcat hc22000 format, GPU-accelerated cracking with dictionary, mask, and rule-based attacks, vendor default-PSK generators (UPC, Sky, BT, etc.), 802.11r FT key cracking, opportunistic key cache analysis, and signal-level optimization. Use when the in-scope network is WPA/WPA2 Personal — the most common consumer/SMB encryption mode. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| offensive-wpa3-saeajtazer/heckitWPA3 / SAE (Simultaneous Authentication of Equals) attack methodology — transition-mode (mixed WPA2/WPA3) downgrade, Dragonblood side-channel attacks (CVE-2019-9494, 9495, 13377, 13456), SAE auth flooding for AP CPU exhaustion, Hash-to-Element (H2E) timing analysis, group downgrade, and 6 GHz / Wi-Fi 6E spec implications (PMF mandatory, no transition mode allowed). Use when target advertises WPA3-SAE or WPA3-Personal/Enterprise, or operates in 6 GHz where WPA3 + PMF are required by spec. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| offensive-wpsajtazer/heckitWPS (Wi-Fi Protected Setup) PIN attack methodology — Pixie Dust offline attack against vulnerable chipsets (Ralink, Realtek, Broadcom, MediaTek), online PIN brute-force with reaver/bully, lockout handling, time-of-day evasion, WPS push-button vulnerability windows, and PIN-to-PSK derivation. Use when a target SOHO router exposes WPS — common on consumer ISP gear, often left enabled by default even when WPS attacks have been known for over a decade. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| offensive-z-waveajtazer/heckitZ-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting Z-Wave smart home devices (door locks, sensors, garage controllers) — common in mid-2010s smart home deployments still in production. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| offensive-zigbee-thread-matterajtazer/heckitZigbee, Thread, and Matter mesh-protocol attack methodology — IEEE 802.15.4 sniffing with TI CC2531 / CC2540 / Sonoff Zigbee Dongle E, KillerBee toolkit, Touchlink commissioning abuse with the well-known transport key, replay/injection attacks, Zigbee Cluster Library command abuse for door locks and bulbs, Thread network credential theft, Matter commissioning chain analysis, and 6LoWPAN/IPv6 routing exploitation. Use when targeting smart-home or commercial mesh deployments, Zigbee-based door locks, lighting, or sensor networks. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| devassuredevassure-ai/devassure-agent-skillsUse when the user wants to install, configure, or run end-to-end web tests with DevAssure CLI (@devassure/cli). Triggers devassure init, devassure plan, devassure ping, devassure test, devassure run, login --confirm, --no-ui, writing YAML test cases, CI/CD token setup, .devassure/ folder structure, DevAssure pricing, or any mention of DevAssure. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| fresh-clonevSkyfall/fresh-cloneTests whether a repository's README actually works by cloning the repo into a throwaway directory (optionally a clean Docker machine) and following the setup instructions exactly like a brand-new user would, running every command for real and timing it. Produces a step-by-step pass/fail report with "time to first run", a list of concrete README improvements with evidence ("add X because…", "remove Y because…"), checks translated READMEs for drift, then walks the user through each fix one at a time and can open a pull request. Use this whenever the user asks to check, test, verify, audit or improve a README, getting-started guide, installation docs or onboarding instructions; whenever they say things like "does my README still work", "would a new contributor get stuck", "my install docs are probably outdated", "someone opened an issue saying setup fails" or "clean up the README"; and before a release or open-sourcing a project. Trigger even if the word README is not used but the request is about whether setup/installation instructions are accurate. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| create-issueby-carlos/plan-staged-rolloutDrafts one GitHub issue or Jira ticket from an ask, has a cheap reviewer challenge its gaps, proposes size or story points and priority, and only after the user approves posts it and verifies what landed. Use when the user says "create an issue", "create a ticket", "draft a Jira story for this", "write this up as a GitHub issue", or asks for a dry run of a ticket. Not for triaging a bug report against existing tickets, turning a spec into a backlog, or pulling tasks out of meeting notes. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |
| staged-rolloutby-carlos/plan-staged-rolloutRun a large build as many small, resumable sessions by decomposing it into a `.plan/` folder of dependency-ordered stages with an evidence ledger, then executing one stage per fresh session. Use when the user says "this is too big for one session", "plan a staged rollout", or describes a multi-day build that needs cross-session progress tracking. | Stars: 1 | Updated | Claude CodeCodex | Unverified | Install |