SkillTide Submit
Official description3 sourcesAgent skills7d ago
morluto/rea

morluto/rea

Local CLI and MCP server for agent-assisted reverse engineering
View on GitHub ↗Direct link · no redirect page
Star count
288,961 ★ · morluto/rea · read from the repository page · (checked 2026-10-16 20:00:20)
Source
read directly from its GitHub page · type: open-source project
Harvest history
first seen 2026-10-10 · last seen 2026-10-16 · seen 7× · listed by 3 sources
Score
score 303 · 288,961 ★ · 3 sources · repo
Install
npx rea-agents
FAQ (answers come from our records)
How do I install it?
The repository provides this install command: npx rea-agents. It comes from the repository itself; we cannot guarantee it runs as-is in your client.
Who is it for?
We filed it under these tags: Agent 技能. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository morluto/rea;first catalogued 2026-10-10;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
Third-party quality signals

**English** · 简体中文 · 繁體中文 · 日本語 · 한국어 · Türkçe · Русский · Tiếng Việt · ไทย · De

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

· Ελληνικά
REA: Reverse Engineer Anything
One MCP for reverse engineering across binaries, applications, and runtime behavior.
**See a feature you like. Understand how it works, down to the binary level.**
**Website · Guides · Showcases**
Quick start · How REA works · What you can analyze · Showcases · FAQ · Documentation
npx rea-agents setup
> [!IMPORTANT]
> Get REA from morluto/rea,
> rea.tools, or the rea-agents npm package.
> Follow the installation and release links from these official sources. A similar
> repository name or copied README does not establish that a download is official.
Join the Reverse Engineering Community
Discord · Q&A · Show and Tell
---
See a feature in an app that you want in your own product? Ask your agent to investigate it with REA. It can inspect the app without its source code, explain how the feature works, show the evidence, and build a version for your project.
REA connects your agent to tools for inspecting native binaries, JavaScript and Electron apps, .NET assemblies, and websites. You can also use the same tools from your terminal. Analysis runs locally, and results include the evidence and limitations behind each conclusion.
Setup registers REA with your agent and installs matching workflow instructions. Native analysis can use an existing Hopper, Ghidra, or IDA installation; setup can optionally install Hopper with approval. Static JavaScript analysis needs no native analysis engine.
> **Visit the REA website** for setup instructions, illustrated guides, and real case studies.
Quick start
On Linux, Ghidra, JADX, firmware tool launches and static JavaScript/Electron
analysis require a procps-compatible ps on REA's PATH for process ownership
checks. Recovery steps are in docs/installation.md under
"Linux owned-process prerequisite".
Set up your agent
With Node.js and npm installed, run:
Choose your agents, review the proposed changes, and approve them. Setup adds
REA's MCP server and matching workflow instructions, with backups of existing
configuration. Restart your agent afterward.
Setup supports Claude Code, Codex, Cursor, Gemini CLI, Grok Build and
other agents. See
installation and setup for provider configuration and
manual MCP registration.
Ask your agent
Replace Notes with your target app and the feature you want to understand.
Use the terminal
Inspect an extracted JavaScript/Electron app directory or ASAR:
The result includes modules, imports, Electron boundaries and their evidence.
Replace the path with your target, such as "D:/apps/example" on Windows.
To install the rea command for regular use:
For native analysis, configure a provider first. See the
CLI and Evidence guide for native commands, provider selection,
snapshots and scripting.
Update REA
REA changes quickly, and new releases include frequent bug fixes. Keep your
installation up to date.
For a CLI installed with npm install --global or bun add --global:
Bun global updates require Bun 1.2.17 or later. With an older Bun release,
upgrade Bun manually before running rea update.
To refresh your agent registrations and skill, run the setup command printed
by the update.
If you use npx, update your agent setup with:
Review the setup changes and restart your agent. For one-off CLI commands,
use npx rea-agents@latest followed by the command. With Bun, use
bunx rea-agents@latest in place of npx rea-agents@latest.
How REA works
Your agent calls REA through MCP to inspect the target and trace relevant code.
REA returns findings with their evidence. The agent uses them to ask follow-up
questions, explain the behavior, or write and test an implementation.
CLI commands use the same workflows.
Open the full-size figure.
What you can analyze
REA requires Node.js 22.x (>=22.19), 24.x (>=24.11), or 26+, plus npm.
Additional tools and host support depend on the target:
| Target | What REA returns | Requirements and guide |
| ---------------------- | ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- |
Source
github · https://github.com/morluto/rea
Browse by field
Agent skills
Traction
288,961 ★
added
yesterday

More in Agent skills

All 142 in Agent skills →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index