# Give agents reverse engineering output they can check, not guess

> borer is an early open-source reverse engineering engine built for agents. It is one Rust binary that runs as an MCP server, keeps lists paged and capped, and checks decompiled C against the machine code in an emulator so the agent knows what is proven.

- URL: https://paperchasewebb.ai/bots/marketplace/items/give-agents-reverse-engineering-output-they-can-check-not-guess/
- Type: Agent use case pack
- Category: Vibe coding
- By: PaperChaseWebb
- Works with: Claude Code, Codex (named in the listing); Plain .md
- Price: Free USD
- Difficulty: Advanced
- Setup time: 1 hr
- Time to result: One working session
- Format: Markdown (.md) file, give-agents-reverse-engineering-output-they-can-check-not-guess.md
- Version: 1.0, updated 2026-10-27
- License: Personal and commercial use. Credit the original source when you share the workflow.

## What you end up with

Three design ideas transfer to any MCP server: cap and page every list, offer a 'since' call so the agent only reads changes, and label results as checked or unchecked.

## What you get

- A plain-language summary of the workflow
- A fill-in prompt template
- What to watch out for
- A link to the original source

## Who it is for

Builders who already use AI agents and want a proven workflow they can copy into their own project.

## Tools needed

- borer: MCP server and CLI for reading binaries
- Any MCP-capable coding agent: asks questions of the binary
- You need: An AI coding agent or chat model
- You need: A small real task to try it on

Cost to run: Free with the agent plan you already use.

## How it works

1. **Install the binary and connect it as an MCP server.** Install the binary and connect it as an MCP server Expected: Done before you move to the next step.
2. **Ask for the functions that touch a given string or import, paged.** Ask for the functions that touch a given string or import, paged Expected: Done before you move to the next step.
3. **Read decompiled C and note which blocks are marked checked.** Read decompiled C and note which blocks are marked checked Expected: Done before you move to the next step.
4. **Treat unchecked blocks as leads to confirm, not facts.** Treat unchecked blocks as leads to confirm, not facts Expected: Done before you move to the next step.
5. **Write what you learned into notes the next session can load.** Write what you learned into notes the next session can load Expected: Done before you move to the next step.

## Sample prompt: Workflow template (borer, Any MCP-capable coding agent)

```
Apply this workflow to [your project]:
1. Install the binary and connect it as an MCP server
2. Ask for the functions that touch a given string or import, paged
3. Read decompiled C and note which blocks are marked checked
4. Treat unchecked blocks as leads to confirm, not facts
5. Write what you learned into notes the next session can load
Stop and ask me before anything irreversible: deploys, payments, sends or deletes.
```

Adapted by PaperChaseWebb. Not the original author's prompt.

## Free preview of give-agents-reverse-engineering-output-they-can-check-not-guess.md

````markdown
# Give agents reverse engineering output they can check, not guess

PaperChase agent use case (free feed entry), version 1.0. Source: [@dear_prism on X (GitHub: imjustprism)](https://x.com/dear_prism/status/2114486515808219316), 2026-10-25.

## What they did

The author argues existing disassemblers were made for a person at a screen, with output sized for eyes rather than a context window. borer exposes about 41 tools that the author puts at roughly 7,000 tokens of definitions. List results are paged and capped, follow-up calls can ask only for what changed since a point, and every block of decompiled C is run in an emulator from seeded states and compared with the original instructions. Anything it cannot model stays marked as raw assembly instead of being guessed, and the output says how much was checked.

## Worth knowing

Three design ideas transfer to any MCP server: cap and page every list, offer a 'since' call so the agent only reads changes, and label results as checked or unchecked. The project warns it is early and tool names may change. Use it only on binaries you have the right to analyze.
````

## Worth knowing

- Three design ideas transfer to any MCP server: cap and page every list, offer a 'since' call so the agent only reads changes, and label results as checked or unchecked. The project warns it is early and tool names may change. Use it only on binaries you have the right to analyze.
- Figures are as reported by the original author and were not re-measured by us.

## Questions

**Where does this come from?** A public post credited to @dear_prism on X (GitHub: imjustprism). Source: https://x.com/dear_prism/status/2114486515808219316

**Is it free?** Yes. Feed entries are free to read and download.

## How to get it

Free sample. Download it directly at https://paperchasewebb.ai/bots/marketplace/items/give-agents-reverse-engineering-output-they-can-check-not-guess/, no signup.

Seller: PaperChaseWebb Inc., mgmt@paperchasewebb.com