rea: reverse engineering driven by agents

TL;DR: rea is a TypeScript CLI that gives coding agents the tools to reverse engineer software, from observing how an app behaves down to reading native binaries. It ships as agent skills, sits at 9,632 stars under MIT, and is a personal project rather than a company one.

What the project is

The description is a single sentence and it sets the scope: reverse engineer anything with agents, from app behavior down to native binaries. That range is the pitch. Most tools in this space occupy one end of it. Dynamic analysis tools watch a program run, disassemblers read bytes off disk, and you usually end up running both by hand.

The published topics back up the lower half of that claim. binary-analysis sits directly alongside agent-skills, ai-agent-tools, ai-agents, and cli.

Field	Value
Language	TypeScript
License	MIT
Stars	9,632
Forks	1,066
Open issues	107
Topics	agent-skills, ai-agent-tools, ai-agents, binary-analysis, cli
Created	2026-04-14
Last push	2026-10-06

The agent skills angle

The topic list is the part worth reading twice. Four of the five entries describe the delivery mechanism rather than the work. Only binary-analysis names what the tool actually does.

That ordering tells you how the project is packaged. This is not a reverse engineering suite with an agent interface bolted on the front. It is distributed as skills that an agent loads on demand, so the surface you touch is whatever client you already run. The presence of cli next to them suggests it stays drivable from a plain terminal when you do not have one.

How to look at it

Clone it and go straight to the skills, since that is where the real contract lives:

git clone https://github.com/morluto/rea.git
cd rea
ls

If you would rather not trust this post, GitHub will tell you the same thing directly:

curl -s https://api.github.com/repos/morluto/rea \
  | jq '{language, topics, license: .license.spdx_id, stars: .stargazers_count}'

When it fits

You are already running an agent against a codebase and you hit a closed binary, an undocumented protocol, or a build step nobody can explain. That is the gap this sits in.

The numbers look healthy for a project five months old. 1,066 forks against 9,632 stars means people are pulling it down rather than just starring it. MIT means commercial use is not a question you need answered before you start.

The maintenance note is that this is a single-owner project. The owner type on GitHub is User, not Organization, so one person is setting the direction.

When it does not fit

If your reverse engineering needs to be defensible in a legal or compliance context, treat any agent-mediated finding as a hypothesis to confirm yourself. The workflow makes speed cheap and independent verification expensive.

Be clear-eyed about one thing I could not verify. A TypeScript project is doing the reversing, and I did not pull the README for this post. So I cannot tell you how the heavy analysis runs, whether it shells out to native tooling, or what the install command is. Check the repository directly before you depend on any of that.

Source and Accuracy Notes

• Project page: https://github.com/morluto/rea
• Source repository: morluto/rea (verified via GitHub API html_url)
• License: MIT (verified via GitHub API license.spdx_id)
• Stars at time of writing: 9,632