An automation skill for controlling web browsers with Playwright and Windows desktop applications with OpenReverse. It can interact with pages and graphical programs through clicks, typing, navigation, screenshots, and related actions.
Use for authorized reverse engineering of browser extensions (Chrome/Firefox) including manifest analysis, background workers, and extension-based credential or traffic logic recovery.
Use for authorized cloud, container, and Kubernetes security assessment including metadata SSRF, IAM misconfig, container escape paths, and cluster RBAC review.
Use for authorized database security assessment covering PostgreSQL/MySQL/MSSQL/Mongo/Redis exposure, authz, UDF/command paths, and misconfiguration review.
Create clear, editable diagrams from messy or structured inputs. Prefer text-based diagram source first so the result can be reviewed, versioned, and refined. Render to files only when the user asks for an image/PDF or when a downloadable artifact would materially help.
Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation. Also use this skill at the END of any completed reverse engineering, penetration testing, CTF, or security analysis task to generate a formal report in the user's…
An authorized red-team and security-testing workflow for studying how endpoint detection and response software monitors Windows programs and for testing targeted evasion techniques.
Use for authorized email security review including phishing analysis, header authentication (SPF/DKIM/DMARC), BEC patterns, and mailbox token abuse research.
A firmware security-testing workflow for examining the software inside routers, cameras, and other connected devices. It starts with a firmware image such as a .bin or .img file and covers analysis, extraction, emulation, and exploit testing.
A repeatable, command-line workflow for using Ghidra to inspect executable files, firmware, and other compiled binaries. Ghidra is a reverse-engineering tool that can recover readable code-like output and program structure.
Use for free/open reverse engineering with Ghidra (headless or GUI), including decompile, cross-refs, and optional Ghidra MCP workflows when IDA is unavailable.
Use for reverse engineering stripped Go and Rust binaries including runtime recognition, pclntab/moduel data recovery, panic strings, and idiomatic decompilation recovery.
Use for authorized hardware and embedded interface security research including UART/JTAG discovery, debug pad triage, secure boot overview, and offline firmware extraction support.
A guide for using IDA Pro to inspect compiled programs and other binary files such as EXE, DLL, ELF, APK, and firmware images. It covers reverse engineering, which means working backward from machine code to understand how software works.
A guide for investigating JavaScript that runs in a web page, including its request-signing logic, runtime values, and connections to browser APIs. It combines source inspection with observing the page while it operates.
Use for authorized security assessment of LLM applications and AI agents, including prompt injection, tool abuse, RAG exposure, memory poisoning, and model supply-chain risks.
Use for authorized macOS and Mach-O reverse engineering including codesign, Objective-C/Swift recovery, endpoint security surfaces, and Apple platform malware analysis.
Use when analyzing suspected malware through static, dynamic, and behavioral techniques, including IOC extraction, YARA or Sigma rules, sandboxing, and anti-analysis behavior.
Use for authorized Android or iOS application reverse engineering and security testing, including APK or IPA analysis, runtime instrumentation, SSL pinning, and platform protection checks.
Use for authorized OT/ICS security assessment covering Purdue model zoning, PLC/SCADA exposure, industrial protocol discovery, and safe passive-first evaluation.
★not rated 2 25d agoA33 tokens
copy · 100%MIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: