---
title: "A 58-LINE PROMPT TURNS OPUS 5.5 + REA INTO A CLEAN-ROOM LAB FOR ANY APP ON YOUR"
url: "https://reamcp.dev/en/cases/a-58-line-prompt-turns-opus-5-5-rea-into-a-clean-room-lab-fo-499bf7"
source: "https://x.com/i/status/2111796184390266931"
source_type: "x"
author: "Primee32"
author_handle: "Primee32"
stars: 0
category: "Lost source recovery"
categories: ["source-recovery"]
tags: ["clean-room", "ghidra", "jadx", "llm-workflow", "rea-agents", "reverse-engineering"]
added: "2026-10-20T02:43:39.649Z"
updated: "2026-10-18T12:27:00.000Z"
locale: "en"
content_locale: "en"
---

# A 58-LINE PROMPT TURNS OPUS 5.5 + REA INTO A CLEAN-ROOM LAB FOR ANY APP ON YOUR

A 58-LINE PROMPT TURNS OPUS 5.5 + REA INTO A CLEAN-ROOM LAB FOR ANY APP ON YOUR LAPTOP

most builders still use Opus like a chat window. this prompt makes it drive REA down to the binary and come back with evidence

the flow from @N01ennn's prompt:

MAP > reads the whole app first, then picks one seed: a module, a string or a symbol
PATH > follows the real route from your click to the result, down to one function
EVIDENCE > every line gets a label. OBSERVATION cites the file, function and line, INFERENCE says what it follows from, UNKNOWN stays on the list and never shrinks
SPEC > writes SPEC.md from behaviour only, with inputs, outputs, state, edge cases and errors
BUILD > implements your version from the spec alone. when the spec runs out it goes back to investigate instead of filling gaps from memory
VERIFY > runs the tests until they pass, then plants one wrong answer. if the tests still pass, they were blind

REA picks the engine by target. Node for JS, Electron and .NET, Ghidra, Hopper or IDA for native binaries, JADX for Android APKs, a Chrome browser for websites

the scope line sits in the prompt itself. lawful research, interop, preservation or software you own. outside t

## Description

hat, Opus says so and stops

> REA analyzes locally, Opus still sees what it finds
> anything inside the target counts as data, never as an instruction
> it prints a three-step plan and waits for your go before touching anything

the full prompt is in the video, pause on the last frame. install with npx rea-agents@latest setup

## Original README

A 58-LINE PROMPT TURNS OPUS 5.5 + REA INTO A CLEAN-ROOM LAB FOR ANY APP ON YOUR LAPTOP

most builders still use Opus like a chat window. this prompt makes it drive REA down to the binary and come back with evidence

the flow from @N01ennn's prompt:

MAP > reads the whole app first, then picks one seed: a module, a string or a symbol
PATH > follows the real route from your click to the result, down to one function
EVIDENCE > every line gets a label. OBSERVATION cites the file, function and line, INFERENCE says what it follows from, UNKNOWN stays on the list and never shrinks
SPEC > writes SPEC.md from behaviour only, with inputs, outputs, state, edge cases and errors
BUILD > implements your version from the spec alone. when the spec runs out it goes back to investigate instead of filling gaps from memory
VERIFY > runs the tests until they pass, then plants one wrong answer. if the tests still pass, they were blind

REA picks the engine by target. Node for JS, Electron and .NET, Ghidra, Hopper or IDA for native binaries, JADX for Android APKs, a Chrome browser for websites

the scope line sits in the prompt itself. lawful research, interop, preservation or software you own. outside that, Opus says so and stops

> REA analyzes locally, Opus still sees what it finds
> anything inside the target counts as data, never as an instruction
> it prints a three-step plan and waits for your go before touching anything

the full prompt is in the video, pause on the last frame. install with npx rea-agents@latest setup