it's f*cking gold
Claude Code can turn reverse engineering into an AI powered investigation lab
18 GitHub tools to inspect Android apps, analyze binaries, trace network traffic, and rebuild software from verified evidence
GIVE AI THE FULL TOOLBOX
01 REA
▸ https://t.co/ujV9V67FwV
→ connect an AI assistant to reverse engineering tools through MCP
DECOMPILE THE CODE
02 Ghidra
▸ https://t.co/wVxkW0voRR
→ decompile binaries and inspect program structure
03 GhidraMCP
▸ https://t.co/3I0CeGHlBS
→ expose Ghidra analysis tools to AI agents
04 IDA Pro MCP
▸ https://t.co/o8riWTkxDJ
→ let agents inspect functions and cross references in IDA
REVERSE ENGINEER MOBILE APPS
05 JADX
▸ https://t.co/kvvIIiZV8b
→ recover Java like source from Android APKs
06 Apktool
▸ https://t.co/5SBiXDDoMd
→ decode and rebuild Android application resources
07 Frida
▸ https://t.co/BlmSnAJkce
→ instrument running applications for dynamic analysis
08 ILSpy
▸ https://t.co/2TtYQC6tDn
→ decompile and inspect .NET assemblies
ANALYZE BINARIES
09 radare2
▸ https://t.co/gsvuHcwC8t
→ inspect machine code, functions, and binary structures
10 x64dbg
▸ https://t.co/pQfkjtxJrE
→ debug Windows applications at runtime
11 ImHex
▸ https://t.co/TEXucLoX7u
→ inspect binary formats with patterns and hex analysis
12 angr
▸ https://t.co/9kKmzlAeD2
→ explore program behavior using symbolic execution
TRACE NETWORK BEHAVIOR
13 mitmproxy
▸ https://t.co/cE8dShyEXW
→ inspect HTTP traffic in authorized test environments
14 dnSpyEx
▸ https://t.co/A2z93kH6SX
→ debug and inspect managed .NET applications
15 rizin
▸ https://t.co/1iAmLulily
→ analyze executable files and disassembly
16 raddebugger
▸ https://t.co/Y9XV04omco
→ debug native programs with a visual interface
REBUILD FROM EVIDENCE
17 Awesome AI Reverse Engineering
▸ https://t.co/B1xd9fVh44
→ discover AI assisted reverse engineering tools
18 Awesome Reverse Engineering
▸ https://t.co/F5X2Bc5LZj
→ find curated resources for binary analysis
Start with software you own or have permission to analyze
1 → Decompile the target with Ghidra or JADX
2 → Collect function names, cross references, and observed behavior
3 → Feed the evidence into Claude Code with a strict analysis prompt
4 → Write SPEC.md describing inputs, outputs, and edge cases
5 → Implement an independent version from the specification
6 → Run comparison tests and repeat until the documented behavior matches
COPY THIS PROMPT:
" Analyze the supplied reverse engineering evidence
Separate verified behavior from assumptions
Produce SPEC.md with inputs, outputs, state transitions, and edge cases
Propose an independent implementation based only on authorized evidence
Generate tests for every documented behavior
Flag anything that cannot be verified "
The expensive part of reverse engineering isn't opening a decompiler
It's turning thousands of disconnected observations into a specification you can actually implement and test
18 tools, one investigation workflow, a reproducible path from evidence to working code
should I write the full guide to building this with Claude Code?
100 futures turned one forecast into trending or choppy.
Kronos. 12 billion K-lines from 45 exchanges. MIT, open weights, runs on a laptop.
→ TOKENIZE OHLCV bars into discrete tokens, same trick as word-level LLMs
→ FORECAST 512 bars in, predict the next 24, sample 100 paths
→ CLASSIFY path spread: tight cluster = trending, wide scatter = choppy
Prediction runs local for free. Edge needs a backtest with real commissions and slippage. This build has none yet. Full ring from tokenizer to rules, running in the terminal below ↓