From an idea to an analysis.

Find out how [feature] works in [app], explain it step by step, and build a similar feature for my project. Use the REA MCP tools. Before you start, confirm with me that I own this target or am authorised to analyse it, and stop if I am not. Show the evidence for every conclusion (files, functions, addresses, requests), say what is still unknown, and do not bypass licence checks, DRM or other protection.

Analyse the Electron app at [absolute path]: list its main and renderer modules, the preload bridge and every IPC channel, and draw how [feature] travels from the UI to the main process. Use the REA MCP tools. Before you start, confirm with me that I own this target or am authorised to analyse it, and stop if I am not. Show the evidence for every conclusion (files, functions, addresses, requests), say what is still unknown, and do not bypass licence checks, DRM or other protection.

In the binary [file], find the function behind [behaviour], read its pseudocode and assembly, and rewrite it as readable C with tests that compare it against the original on sample inputs. Use the REA MCP tools. Before you start, confirm with me that I own this target or am authorised to analyse it, and stop if I am not. Show the evidence for every conclusion (files, functions, addresses, requests), say what is still unknown, and do not bypass licence checks, DRM or other protection.

Work out the structure of the [extension] files that [program] reads and writes: header, sections, field types and offsets. Write a specification and a small parser that round-trips my sample files. Use the REA MCP tools. Before you start, confirm with me that I own this target or am authorised to analyse it, and stop if I am not. Show the evidence for every conclusion (files, functions, addresses, requests), say what is still unknown, and do not bypass licence checks, DRM or other protection.

Read the saved capture [HAR or capture file] of my own app talking to its server, group the requests by endpoint, describe each payload, and write a client for the documented calls. Use the REA MCP tools. Before you start, confirm with me that I own this target or am authorised to analyse it, and stop if I am not. Show the evidence for every conclusion (files, functions, addresses, requests), say what is still unknown, and do not bypass licence checks, DRM or other protection.

Inspect the APK of my app at [path]: list the manifest declarations, exported components, native libraries and third-party SDKs, and flag anything I did not expect to ship. Use the REA MCP tools. Before you start, confirm with me that I own this target or am authorised to analyse it, and stop if I am not. Show the evidence for every conclusion (files, functions, addresses, requests), say what is still unknown, and do not bypass licence checks, DRM or other protection.

Compare the .NET assemblies [old build] and [new build] of my project: changed types and methods, CIL differences in [area], and new native dependencies. Summarise what changed and why it might matter. Use the REA MCP tools. Before you start, confirm with me that I own this target or am authorised to analyse it, and stop if I am not. Show the evidence for every conclusion (files, functions, addresses, requests), say what is still unknown, and do not bypass licence checks, DRM or other protection.

I lost the source of my program [name]; only the compiled [file] is left. Recover its structure: modules, key functions and data, and rebuild readable source for [part], marking every guess. Use the REA MCP tools. Before you start, confirm with me that I own this target or am authorised to analyse it, and stop if I am not. Show the evidence for every conclusion (files, functions, addresses, requests), say what is still unknown, and do not bypass licence checks, DRM or other protection.

Statically triage the sample [file] that reached our systems, inside an isolated environment and without running it: strings, imports, likely capabilities and indicators of compromise we can use for detection. Use the REA MCP tools. Before you start, confirm with me that I own this target or am authorised to analyse it, and stop if I am not. Show the evidence for every conclusion (files, functions, addresses, requests), say what is still unknown, and do not bypass licence checks, DRM or other protection.

Help me with the CTF reversing challenge [name]: walk through the binary, explain the check it performs and how to derive the expected input, so I learn the technique rather than just the flag. Use the REA MCP tools. Before you start, confirm with me that I own this target or am authorised to analyse it, and stop if I am not. Show the evidence for every conclusion (files, functions, addresses, requests), say what is still unknown, and do not bypass licence checks, DRM or other protection.

Read the build information embedded in the Go binary [file] we ship: compiler version, modules and versions, replacements and build settings, and compare them with our go.mod and release notes. Use the REA MCP tools. Before you start, confirm with me that I own this target or am authorised to analyse it, and stop if I am not. Show the evidence for every conclusion (files, functions, addresses, requests), say what is still unknown, and do not bypass licence checks, DRM or other protection.

Open [URL of my site] in a Chrome-family browser, record the scripts and network requests, and explain how [section] gets its data and what slows it down. Use the REA MCP tools. Before you start, confirm with me that I own this target or am authorised to analyse it, and stop if I am not. Show the evidence for every conclusion (files, functions, addresses, requests), say what is still unknown, and do not bypass licence checks, DRM or other protection.