Reverse Engineering (REA)

Reverse engineer shipped software from a coding agent with REA (Reverse Engineer Anything): native binaries, JavaScript and Electron apps, .NET assemblies, Android APKs, firmware, WebAssembly, EVM bytecode, saved network captures and running browser pages. Every conclusion comes back with its evidence and its unknowns, so the agent can explain how a feature works and build a similar one.

Start by asking about a target, for example: "Explain how search works in /Applications/Notes.app and show the evidence". The reverse-engineer-anything skill picks the right REA tool for the target, works summary-first and keeps a finding ledger; the rea MCP server does the analysis locally.

Third-party, included unmodified: the reverse-engineer-anything skill (with its reference guides) and the rea-agents MCP server, both from https://github.com/morluto/rea (MIT). Not affiliated with the REA authors.

Prerequisites: Node.js 22.19+, 24.11+ or 26+ (the MCP server runs with npx). Static JavaScript, .NET, Go and archive inspection need nothing else. Native decompilation needs Hopper, Ghidra (free) or IDA, installed by you; Android needs headless JADX and a full JDK; firmware needs Binwalk or Unblob; some targets need WABT, pwntools or a Chrome-family browser. No account or API key; Hopper and IDA are paid products.

For software you own or are authorized to examine: security and malware research, interoperability, debugging, CTFs. Not for circumventing DRM, licence checks or anti-cheat, or for copying proprietary code — the setup's rules hold the agent to that.