Reverse-engineer apps and binaries with REA
Connect coding agents to REA's MCP tools so they can inspect apps, binaries, websites, APKs, and runtime behavior with evidence-backed findings.
npx skills add agentskillexchange/skills --skill reverse-engineer-apps-and-binaries-with-rea
npx rea-agents setup, choose the supported agents to configure, review the proposed MCP and instruction changes, approve them, and restart the agent. For CLI-only use, run npm install --global rea-agents and then rea --help.Use REA when an agent needs to understand how a local application, binary, website, package, or captured runtime behavior works before explaining or rebuilding a feature. The workflow installs the REA MCP server and matching agent instructions, points the agent at an authorized target, and asks for evidence-backed analysis with known limitations. This belongs in ASE because the operator action is a repeatable reverse-engineering investigation for agents, not a generic reverse-engineering product listing. Keep the scope to permitted local analysis, interoperability, debugging, and learning workflows.
What this skill actually does
Inputs and prerequisites: Node.js 22.19+ or newer, npm, an MCP-capable agent, and optional analysis tools such as Hopper, Ghidra, IDA, Chrome, JADX, binwalk, or Unblob depending on the target..
Setup notes: Run npx rea-agents setup , choose the supported agents to configure, review the proposed MCP and instruction changes, approve them, and restart the agent. For CLI-only use, run npm install –global rea-agents and then rea –help .
Source and verification boundary: use https://morluto.github.io/rea/ as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a MCP workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.