rea
Reverse engineer anything with agents, from app behavior down to native binaries.
Runs with mockssource: GitHubTypeScriptMITcommit 2160d4fae581
TypeScript, MIT licensed. The project labels itself: agent skills, ai agent tools, ai agents, binary analysis, cli, coding agent, coding agents and cordis.
rea runs, with stand-ins for the services it depends on. An Argusic agent installed it in 3 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
REA compiles and runs on Node.js 22.19.0 with npm 11.16.0. The full TypeScript build succeeds, all 353 Vitest test files (1756 individual tests) pass covering domain logic, adapters, composition, MCP boundary, acceptance, conformance, and evaluation layers, and the CLI lists all 60+ analysis commands without error.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
- Install time
- 3 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- npm test exited 0, 353 test files passed with 1756 tests passing; node scripts/rea.mjs --help displayed 60+ commands successfully
- Model tokens used
- 206,472
- Exact commit tested
- 2160d4fae581
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
--help Show help --llms, --llms-full Print LLM-readable manifest --mcp Start as MCP stdio server --schema Show JSON Schema for command --token-count Print token count of output (instead of output) --token-limit <n> Limit output to n tokens --token-offset <n> Skip first n tokens of output --version Show version The CLI started and showed all commands. Here's the final report: tokens used 206,472 The CLI started and showed all commands. Here's the final report:
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 3 minutes.
- Nothing broke on the way: zero errors between clone and running.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 37 agent-skills projects Argusic has installed and timed, rea was the 18th fastest to reach a running state, and 27 of 37 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.03 |
Topics (from GitHub)
agent-skillsai-agent-toolsai-agentsbinary-analysisclicoding-agentcoding-agentscordisdecompilerdisassemblerdshdsh-pluginhopper-disassemblermcpmcp-servermodel-context-protocolreverse-engineeringreverse-engineering-toolsstatic-analysis
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/rea)Questions
- Does rea run?
- rea runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test rea?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2160d4fae581. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test rea?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does rea take to install?
- 3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does rea need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing rea?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does rea compare with the alternatives?
- Of the 37 agent-skills projects Argusic has installed and timed, rea was the 18th fastest to reach a running state, and 27 of 37 reached one at all.
- Where is the evidence for rea?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.