Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

this is getting f*cking dangerous... REA creator just dropped 20 GitHub repos to build a f*cking reverse engineering studio: [01] analysis core > REA: a single MCP that plugs into everything > Ghidra: decompiler, free > GhidraMCP: lets your agent drive Ghidra > ida-pro-mcp: hooks your agent into IDA...

0xDeniAi's profile picture

Deni

3,589 subscribers

236,466 görüntüleme • 14 gün önce •via X (Twitter)

Bilim & Teknoloji
LIVE

Anya Rossi• Live Now

Private livecam show

20 Yorum

Homunculus profil fotoğrafı
Homunculus13 gün önce

Is it still working?

Billy profil fotoğrafı
Billy13 gün önce

But it still needs a lot of work to achieve something useful

Brett Cooper profil fotoğrafı
Brett Cooper13 gün önce

But what if the hardware driver support ended with win98...

kelvin profil fotoğrafı
kelvin13 gün önce

This is a serious toolkit for anyone getting into reverse engineering. The clean-room rebuild and verification loop is especially interesting. Can REA handle complex apps, or does it work best with smaller projects?

Yasin profil fotoğrafı
Yasin13 gün önce

at this point are any apps even safe? 20 repos of RE study material says the answer is no lol

The Tinfôil Tricõrn 🇺🇸 profil fotoğrafı
The Tinfôil Tricõrn 🇺🇸13 gün önce

Literally not dangerous, it's the whole history of technology, evaluation, science and academic work. What is dangerous is "black boxes" running unknown illegal pipelines to foreign nations. Always on recording devices violating state laws and so on. TOS do not obviate a reasonable expectation of privacy.

Scotty profil fotoğrafı
Scotty13 gün önce

@fawk_bot review and asses.

Sharon Daniel ©️🎭 profil fotoğrafı
Sharon Daniel ©️🎭13 gün önce

But I thought Anthropic stoped Claud from using that repo. It will not work ??

AIBotics profil fotoğrafı
AIBotics13 gün önce

the clean room rebuild loop is the wild part AI can now speedrun the whole reverse engineering workflow instead of just explaining code

JoeCat ® profil fotoğrafı
JoeCat ®13 gün önce

Smh

tony profil fotoğrafı
tony13 gün önce

@threadreaderapp unroll

0xbobaa profil fotoğrafı
0xbobaa13 gün önce

ghidra + jadx + frida already covers most mobile apps, REA as the MCP glue is what turns 3 tools into one loop

Toni Cipirani profil fotoğrafı
Toni Cipirani13 gün önce

@grok is the gif even possible to do or is this guy full of shit?

kk profil fotoğrafı
kk13 gün önce

@bot 看看，发给我

Ayslânia profil fotoğrafı
Ayslânia13 gün önce

试试看

Evan Johnson profil fotoğrafı
Evan Johnson13 gün önce

This is why the internet is about to be shutdown. Can you all stop 🛑

离岸工具包🎒 profil fotoğrafı
离岸工具包🎒13 gün önce

Hey there! Just dropping in to say, "Wow, that's some serious dedication to the craft! 🤩 Impressive to see someone pushing the boundaries with reverse engineering. It's moments like these that remind us why we love being part of this incredible tech community. Let's keep the learning and support flowing. Here's to pushing the limits and connecting over shared passions! 🚀💻🌟

Nilo profil fotoğrafı
Nilo13 gün önce

brilliant move

Don Codeleone profil fotoğrafı
Don Codeleone13 gün önce

"dangerous" ....😂😂😂😂 First time hacking?

Tralalero Tralalala profil fotoğrafı
Tralalero Tralalala13 gün önce

OMG my wettest dream

Benzer Videolar

this is getting f*cking dangerous... REA creator just dropped 20 GitHub repos to build a f*cking reverse engineering studio: [01] analysis core [02] mobile & apps [03] binary & low-level [04] network & runtime [05] rebuild & verify how it runs: binary -> REA -> SPEC.md -> rebuild -> oracle -> retry point it at any app and watch it explain itself.
0:22

this is getting f*cking dangerous... REA creator just dropped 20 GitHub repos to build a f*cking reverse engineering studio: [01] analysis core [02] mobile & apps [03] binary & low-level [04] network & runtime [05] rebuild & verify how it runs: binary -> REA -> SPEC.md -> rebuild -> oracle -> retry point it at any app and watch it explain itself.

Deni

142,959 görüntüleme • 23 gün önce

this is pure f*cking treasure REA creator just dropped 20 GitHub repos to build a f*cking reverse engineering studio: 01 / analysis core 02 / mobile & apps 03 / binary & low-level 04 / network & runtime 05 / rebuild & verify the loop: binary -> REA -> SPEC.md -> rebuild -> oracle -> retry study the original. ship your own.
0:22

this is pure f*cking treasure REA creator just dropped 20 GitHub repos to build a f*cking reverse engineering studio: 01 / analysis core 02 / mobile & apps 03 / binary & low-level 04 / network & runtime 05 / rebuild & verify the loop: binary -> REA -> SPEC.md -> rebuild -> oracle -> retry study the original. ship your own.

NO1ennn

33,871 görüntüleme • 24 gün önce

This is getting f*cking scary. 15 GitHub repos now wrap REA in a desktop studio, a local-model plugin and a scanner that shows what it could pull out of your own app [01] wrappers and installs ERA: wraps REA with run records, reports and a desktop studio reverseport: turns findings into rebuild specs and ports between engines and languages rea-mcp: REA inside LM Studio for local models rea-flake: REA with Ghidra packaged for Nix [02] check and defend reaproof: scans your own build for what REA could recover, like source maps and keys antirea: stop directives that tell agents not to run REA on your project REA-demo: REA analyzing its own package, graded against the source [03] worked examples OpenBSD_netcat_REA: a static analysis of netcat-openbsd, every claim linked to an evidence file hexgrab: a color picker written from REA’s study of PowerToys behavior, with no PowerToys code [04] reading rea-research: a deep write-up of REA’s architecture and trust model, in Chinese reatool: unofficial install guides and a comparison with GhidraMCP and ida-pro-mcp [05] maps Awesome-REA: a bilingual catalogue of REA tools, cases and papers awesome-rea: every entry names its own acceptance test rea-case-rankings: cases from GitHub, HN, X and Reddit on a 1 to 5 score rea-gems: an auto-updated gallery of REA cases how the loop runs: app -> REA -> findings -> spec -> rebuild -> check -> harden start with an app you own and watch it explain itself.
0:24

This is getting f*cking scary. 15 GitHub repos now wrap REA in a desktop studio, a local-model plugin and a scanner that shows what it could pull out of your own app [01] wrappers and installs ERA: wraps REA with run records, reports and a desktop studio reverseport: turns findings into rebuild specs and ports between engines and languages rea-mcp: REA inside LM Studio for local models rea-flake: REA with Ghidra packaged for Nix [02] check and defend reaproof: scans your own build for what REA could recover, like source maps and keys antirea: stop directives that tell agents not to run REA on your project REA-demo: REA analyzing its own package, graded against the source [03] worked examples OpenBSD_netcat_REA: a static analysis of netcat-openbsd, every claim linked to an evidence file hexgrab: a color picker written from REA’s study of PowerToys behavior, with no PowerToys code [04] reading rea-research: a deep write-up of REA’s architecture and trust model, in Chinese reatool: unofficial install guides and a comparison with GhidraMCP and ida-pro-mcp [05] maps Awesome-REA: a bilingual catalogue of REA tools, cases and papers awesome-rea: every entry names its own acceptance test rea-case-rankings: cases from GitHub, HN, X and Reddit on a 1 to 5 score rea-gems: an auto-updated gallery of REA cases how the loop runs: app -> REA -> findings -> spec -> rebuild -> check -> harden start with an app you own and watch it explain itself.

Ryven

42,774 görüntüleme • 9 gün önce

It is becoming f*cking dangerous: the NSA's own reverse-engineering tool now plugs straight into Claude Code - Ghidra has 94k stars, and GhidraMCP lets your agent read a compiled program instead of guessing what it does Install Ghidra 12.1.4 from ghidra-sre,org (free, released by the NSA) Download the GhidraMCP release and add it in File -> Install Extensions Restart Ghidra and switch on GhidraMCPPlugin in File -> Configure -> Developer Connect it: claude mcp add ghidra -- uvx --from git+ ghidra-mcp Open a binary you're allowed to analyze and let Ghidra run its analysis Ask Claude what a function does: it decompiles it, renames the variables and explains it in plain English Ask for the map: every function, import, string and cross-reference, and where the interesting code lives The decompiling runs in Ghidra on your machine, Claude just drives it Malware samples, old firmware, your own builds: your agent reads the program itself, not the docs about it Find the repo in the reply below
0:20

It is becoming f*cking dangerous: the NSA's own reverse-engineering tool now plugs straight into Claude Code - Ghidra has 94k stars, and GhidraMCP lets your agent read a compiled program instead of guessing what it does Install Ghidra 12.1.4 from ghidra-sre,org (free, released by the NSA) Download the GhidraMCP release and add it in File -> Install Extensions Restart Ghidra and switch on GhidraMCPPlugin in File -> Configure -> Developer Connect it: claude mcp add ghidra -- uvx --from git+ ghidra-mcp Open a binary you're allowed to analyze and let Ghidra run its analysis Ask Claude what a function does: it decompiles it, renames the variables and explains it in plain English Ask for the map: every function, import, string and cross-reference, and where the interesting code lives The decompiling runs in Ghidra on your machine, Claude just drives it Malware samples, old firmware, your own builds: your agent reads the program itself, not the docs about it Find the repo in the reply below

Archive

16,420 görüntüleme • 16 gün önce

THIS IS F**KING DANGEROUS someone built an AI skill for Android APK reverse engineering. → decompile and analyze apps → patch DEX files and remove ads → rebuild APKs and debug at runtime you can also run Android games on PC using an emulator, then use reverse engineering tools to investigate how they work. install the skill: npx skills add newliver666/apk-reverse your AI agent just became an Android reverse engineering assistant. only test apps you own or have permission to assess. REPO BELOW
1:00

THIS IS F**KING DANGEROUS someone built an AI skill for Android APK reverse engineering. → decompile and analyze apps → patch DEX files and remove ads → rebuild APKs and debug at runtime you can also run Android games on PC using an emulator, then use reverse engineering tools to investigate how they work. install the skill: npx skills add newliver666/apk-reverse your AI agent just became an Android reverse engineering assistant. only test apps you own or have permission to assess. REPO BELOW

MAX

98,741 görüntüleme • 25 gün önce

THIS IS A PURE F*CKING GOLDMINE the best REA trick almost nobody runs yet. The idea: REA takes the app apart, Jev keeps only what's proven, and a fresh Opus 5.5 rebuilds the feature from that alone. Nothing gets copied and no guess makes it into the code, because the builder never sees the original, only the spec Jev signed off on. You just connect REA like this: npx rea-agents setup here's the split: → REA reads the feature down to the binary and writes every rule into SPEC.md → Jev checks each rule against REA's evidence and sends back anything unproven → a fresh Opus 5.5 session gets only SPEC.md and rebuilds the feature → Haiku 5.5 runs the tests against 3 intentionally broken versions Opus only shows up at three moments: → rebuilding from the approved spec → the checks Jev marks as unclear → signing off before anything ships REA reads. Jev judges. Opus rebuilds. That's the clean-room rule in one line: the model that saw the original never writes the code, and the model that writes the code never sees the original. the full tree > REA reads the app and writes SPEC.md with evidence for every rule > Jev approves or returns each rule > Opus 5.5 rebuilds from the approved SPEC.md in a fresh session > Haiku 5.5 runs the tests and the 3 broken versions > Jev routes unclear checks back to Opus > /goal keeps going until all 3 broken versions fail paste the tree and this prompt into Claude Code ↓ "Set up a clean-room rebuild around this tree: 1. Use REA to investigate [FEATURE] in [APP]. Write every behavior and rule into SPEC.md, each with the evidence REA found. 2. Send each rule to Jev. Any rule without evidence goes back to REA. 3. Start a fresh session with only SPEC.md. Rebuild the feature on Opus 5.5 without opening the original. 4. Write tests on Haiku 5.5 plus 3 intentionally broken versions. Use /goal until the rebuild passes and all 3 broken versions fail. Show me SPEC.md first. Nothing gets built until I say go." ↳ save it, it'll come in handy.
0:20

THIS IS A PURE F*CKING GOLDMINE the best REA trick almost nobody runs yet. The idea: REA takes the app apart, Jev keeps only what's proven, and a fresh Opus 5.5 rebuilds the feature from that alone. Nothing gets copied and no guess makes it into the code, because the builder never sees the original, only the spec Jev signed off on. You just connect REA like this: npx rea-agents setup here's the split: → REA reads the feature down to the binary and writes every rule into SPEC.md → Jev checks each rule against REA's evidence and sends back anything unproven → a fresh Opus 5.5 session gets only SPEC.md and rebuilds the feature → Haiku 5.5 runs the tests against 3 intentionally broken versions Opus only shows up at three moments: → rebuilding from the approved spec → the checks Jev marks as unclear → signing off before anything ships REA reads. Jev judges. Opus rebuilds. That's the clean-room rule in one line: the model that saw the original never writes the code, and the model that writes the code never sees the original. the full tree > REA reads the app and writes SPEC.md with evidence for every rule > Jev approves or returns each rule > Opus 5.5 rebuilds from the approved SPEC.md in a fresh session > Haiku 5.5 runs the tests and the 3 broken versions > Jev routes unclear checks back to Opus > /goal keeps going until all 3 broken versions fail paste the tree and this prompt into Claude Code ↓ "Set up a clean-room rebuild around this tree: 1. Use REA to investigate [FEATURE] in [APP]. Write every behavior and rule into SPEC.md, each with the evidence REA found. 2. Send each rule to Jev. Any rule without evidence goes back to REA. 3. Start a fresh session with only SPEC.md. Rebuild the feature on Opus 5.5 without opening the original. 4. Write tests on Haiku 5.5 plus 3 intentionally broken versions. Use /goal until the rebuild passes and all 3 broken versions fail. Show me SPEC.md first. Nothing gets built until I say go." ↳ save it, it'll come in handy.

Archive

59,706 görüntüleme • 24 gün önce

HOLY F*CK, can't believe my eyes, someone leaked an entire reverse engineering degree on GitHub. This free stack completely automates dissecting closed binaries, applications, and firmware using AI agents: 1. radare2 → Full binary analysis straight in the terminal. Replaces heavy GUI tools and lets you tear through code via scripts and CLI. Instant execution file analysis on remote headless servers. ↳ 2. Ghidra → Free decompiler matching high-end enterprise suites. NSA's open-source tool that completely covers commercial decompiler needs. Visual call graphs, structured control flow, and automated logic recovery. ↳ 3. LLM4Decompile → Neural machine code translation into clean C. Specialized model that reconstructs variables and function structures after compiler passes. Turns stripped assembly into readable source code in seconds. ↳ 4. r2ai → Local AI copilot embedded in your terminal debugger. Integrates language models directly into your active session without external chat switching. Explains dense logic and flags cryptographic routines or bugs during live execution. ↳ 5. reverse-engineering-assistant → Bridge Ghidra to AI agents via MCP. Model Context Protocol server opening symbols, functions, and memory to external LLMs. Lets Claude Code or Cursor explore target codebases and deobfuscate variables autonomously. ↳ 6. ida-pro-mcp → Full IDA Pro orchestration without manual clicking. Drives the industry-standard decompiler over Model Context Protocol. Delegates xref tracing, batch symbol mapping, and binary patching directly to agents. ↳ 7. REA → Autonomous software reverse engineering on autopilot. Engine handling 35 target types: native binaries, Android APKs, Electron apps, and firmware. Ingests a closed-source target, pinpoints target features, and generates verifiable evidence for replication. ↳ Analysis → Disassembly → Neural Decompilation → MCP Bridge → Autonomous Report. Bookmark this. The era of manual bytecode grinding is over ↓
0:32

HOLY F*CK, can't believe my eyes, someone leaked an entire reverse engineering degree on GitHub. This free stack completely automates dissecting closed binaries, applications, and firmware using AI agents: 1. radare2 → Full binary analysis straight in the terminal. Replaces heavy GUI tools and lets you tear through code via scripts and CLI. Instant execution file analysis on remote headless servers. ↳ 2. Ghidra → Free decompiler matching high-end enterprise suites. NSA's open-source tool that completely covers commercial decompiler needs. Visual call graphs, structured control flow, and automated logic recovery. ↳ 3. LLM4Decompile → Neural machine code translation into clean C. Specialized model that reconstructs variables and function structures after compiler passes. Turns stripped assembly into readable source code in seconds. ↳ 4. r2ai → Local AI copilot embedded in your terminal debugger. Integrates language models directly into your active session without external chat switching. Explains dense logic and flags cryptographic routines or bugs during live execution. ↳ 5. reverse-engineering-assistant → Bridge Ghidra to AI agents via MCP. Model Context Protocol server opening symbols, functions, and memory to external LLMs. Lets Claude Code or Cursor explore target codebases and deobfuscate variables autonomously. ↳ 6. ida-pro-mcp → Full IDA Pro orchestration without manual clicking. Drives the industry-standard decompiler over Model Context Protocol. Delegates xref tracing, batch symbol mapping, and binary patching directly to agents. ↳ 7. REA → Autonomous software reverse engineering on autopilot. Engine handling 35 target types: native binaries, Android APKs, Electron apps, and firmware. Ingests a closed-source target, pinpoints target features, and generates verifiable evidence for replication. ↳ Analysis → Disassembly → Neural Decompilation → MCP Bridge → Autonomous Report. Bookmark this. The era of manual bytecode grinding is over ↓

Hoodie

35,938 görüntüleme • 7 gün önce

FREE ANDROID APK REVERSE ENGINEERING SKILL FOR AI AGENTS 💀 someone used AI to reverse engineer Android apps and build modded game APKs what you'll get • APK analysis and decompilation • ad removal and dex patching • repacking and runtime debugging how to get it 1. go to 2. run npx skills add newliver666/apk-reverse 3. let your AI agent handle the workflow basically, your AI agent becomes an Android reverse engineering assistant
0:22

FREE ANDROID APK REVERSE ENGINEERING SKILL FOR AI AGENTS 💀 someone used AI to reverse engineer Android apps and build modded game APKs what you'll get • APK analysis and decompilation • ad removal and dex patching • repacking and runtime debugging how to get it 1. go to 2. run npx skills add newliver666/apk-reverse 3. let your AI agent handle the workflow basically, your AI agent becomes an Android reverse engineering assistant

Peng

218,038 görüntüleme • 27 gün önce

Reverse engineering with REA + Opus 5.5 takes any program apart piece by piece, and it's f**king unreal websites, games, apps what took years, REA now takes apart in one evening and copies everything without you writing a single line of code this file turns Claude into a system that knows everything: 1,143 files, 7,449 functions, every button first it reads the whole thing, over 1,000 files and thousands of pieces of code, and marks everything that still needs checking Opus 5.5 plans, Sonnet 5.5 does most of the work and a cheap Haiku finds the right spots in the code, so the expensive model only switches on when it has to think then REA opens the program itself, clicks the buttons and watches what happens on screen a second Opus 5.5 checks every conclusion and only lets through what's proven findings are saved between sessions, so tomorrow it picks up right where it stopped REA doesn't copy anyone's code. it explains how every button works, helps you write your own version from scratch and tests it against the original save it before you pay for your next tool ↓
0:49

Reverse engineering with REA + Opus 5.5 takes any program apart piece by piece, and it's f**king unreal websites, games, apps what took years, REA now takes apart in one evening and copies everything without you writing a single line of code this file turns Claude into a system that knows everything: 1,143 files, 7,449 functions, every button first it reads the whole thing, over 1,000 files and thousands of pieces of code, and marks everything that still needs checking Opus 5.5 plans, Sonnet 5.5 does most of the work and a cheap Haiku finds the right spots in the code, so the expensive model only switches on when it has to think then REA opens the program itself, clicks the buttons and watches what happens on screen a second Opus 5.5 checks every conclusion and only lets through what's proven findings are saved between sessions, so tomorrow it picks up right where it stopped REA doesn't copy anyone's code. it explains how every button works, helps you write your own version from scratch and tests it against the original save it before you pay for your next tool ↓

Noisy

13,006 görüntüleme • 27 gün önce

The dirty little secret every founder is hiding: your app isn't private anymore you know that feature you're proud of? the one that took your team months? an AI agent can now open your app, take it apart and tell anyone exactly how it works. just a free tool called REA. Reverse Engineer Anything. 352k stars on GitHub. setup is one line: npx rea-agents setup then you type something like this into Claude Code: "Understand how search works in the Notes app, show me the evidence, and build a similar feature for my project." that's it. it digs in, shows its work, and writes a version for you. what it can open: -> native apps, with Ghidra, Hopper or IDA under the hood -> JavaScript and Electron apps -> .NET apps -> websites everything runs on your own machine. now the part nobody wants to say out loud: copying a product used to be hard. that was the real protection. not patents. not secrecy. effort. the effort is gone. what's left that no agent can copy? your users. your speed. your taste. if your startup only survives as long as nobody understands how it works, it was never a business. it was a head start. founders are going to hate this one save it. send it to the founder who thinks their moat is the code.
0:25

The dirty little secret every founder is hiding: your app isn't private anymore you know that feature you're proud of? the one that took your team months? an AI agent can now open your app, take it apart and tell anyone exactly how it works. just a free tool called REA. Reverse Engineer Anything. 352k stars on GitHub. setup is one line: npx rea-agents setup then you type something like this into Claude Code: "Understand how search works in the Notes app, show me the evidence, and build a similar feature for my project." that's it. it digs in, shows its work, and writes a version for you. what it can open: -> native apps, with Ghidra, Hopper or IDA under the hood -> JavaScript and Electron apps -> .NET apps -> websites everything runs on your own machine. now the part nobody wants to say out loud: copying a product used to be hard. that was the real protection. not patents. not secrecy. effort. the effort is gone. what's left that no agent can copy? your users. your speed. your taste. if your startup only survives as long as nobody understands how it works, it was never a business. it was a head start. founders are going to hate this one save it. send it to the founder who thinks their moat is the code.

kiosa

11,958 görüntüleme • 17 gün önce

Anthropic is furious: this secret tool can replicate any existing app x10 faster for free there's an open-source tool with 352k stars on GitHub that lets an AI agent take apart any app you have on your machine and explain exactly how a feature works. no source code needed. it's called REA. Reverse Engineer Anything. one line: npx rea-agents setup then you just ask Claude Code: "Understand how search works in the Notes app, show me the evidence, and build a similar feature for my project." and it does it. -> native binaries, through Ghidra, Hopper or IDA -> JavaScript and Electron apps -> .NET apps -> websites it runs locally. it shows its evidence. then it writes the code. that feature your team spent 8 months on? someone's agent can read how it works over lunch. so let's be honest about what this means: your moat was never the code. it was that copying you took effort. that effort just went to zero. the only things left that can't be cloned: your users, your speed, and your taste. and if your product dies because someone could see how it works, it was already dead. the repo is below. founders, you're going to hate this one save, share, and try later
0:25

Anthropic is furious: this secret tool can replicate any existing app x10 faster for free there's an open-source tool with 352k stars on GitHub that lets an AI agent take apart any app you have on your machine and explain exactly how a feature works. no source code needed. it's called REA. Reverse Engineer Anything. one line: npx rea-agents setup then you just ask Claude Code: "Understand how search works in the Notes app, show me the evidence, and build a similar feature for my project." and it does it. -> native binaries, through Ghidra, Hopper or IDA -> JavaScript and Electron apps -> .NET apps -> websites it runs locally. it shows its evidence. then it writes the code. that feature your team spent 8 months on? someone's agent can read how it works over lunch. so let's be honest about what this means: your moat was never the code. it was that copying you took effort. that effort just went to zero. the only things left that can't be cloned: your users, your speed, and your taste. and if your product dies because someone could see how it works, it was already dead. the repo is below. founders, you're going to hate this one save, share, and try later

kiosa

52,433 görüntüleme • 19 gün önce

these 2 free GitHub repos should honestly be illegal in trading - they just made a $30K/year terminal obsolete hedge funds pay $30K a year per seat for a Bloomberg terminal - someone rebuilt one with 2 GitHub repos and made every chart draw 100 possible futures for 100% FREE the repos are REA and Kronos. REA hit #1 on GitHub and has 200k stars. Kronos was trained on 12 BILLION candles, the paper got into AAAI 2026, and it has 41k stars first understand how it works: > REA lets your AI agent see how any app works, down to the binary, and rebuild it from scratch > ChatGPT turns words into tokens & predicts the next word > Kronos turns every candle into tokens & predicts the NEXT CANDLE > in the paper's benchmarks it beat the best rival model's forecasts by 93% > put them together and you get a Bloomberg-style terminal where every chart forecasts itself here is how to build it yourself for FREE: 1. open Claude Code and connect REA as an MCP. it maps how the terminal works: quotes, charts, news, screeners 2. ask Claude to rebuild every panel from scratch. equities, FX, commodities, crypto, live news feed 3. pull the data from free public APIs. Binance gives you any coin, any timeframe, no account 4. clone and load Kronos-small. 24.7M params, it runs on a normal laptop, no GPU 5. feed it the last 512 candles and ask for the next 24, exactly like an LLM finishing a sentence 6. sample 100 futures, not one guess, and draw all of them right on the chart. the spread shows how risky the next move really is 7. read the regime: most paths pointing one way means TRENDING, paths scattered both ways means CHOPPY 8. backtest it walk-forward with real fees and paper trade it before you trust a single path i won't say anything more:
0:30

these 2 free GitHub repos should honestly be illegal in trading - they just made a $30K/year terminal obsolete hedge funds pay $30K a year per seat for a Bloomberg terminal - someone rebuilt one with 2 GitHub repos and made every chart draw 100 possible futures for 100% FREE the repos are REA and Kronos. REA hit #1 on GitHub and has 200k stars. Kronos was trained on 12 BILLION candles, the paper got into AAAI 2026, and it has 41k stars first understand how it works: > REA lets your AI agent see how any app works, down to the binary, and rebuild it from scratch > ChatGPT turns words into tokens & predicts the next word > Kronos turns every candle into tokens & predicts the NEXT CANDLE > in the paper's benchmarks it beat the best rival model's forecasts by 93% > put them together and you get a Bloomberg-style terminal where every chart forecasts itself here is how to build it yourself for FREE: 1. open Claude Code and connect REA as an MCP. it maps how the terminal works: quotes, charts, news, screeners 2. ask Claude to rebuild every panel from scratch. equities, FX, commodities, crypto, live news feed 3. pull the data from free public APIs. Binance gives you any coin, any timeframe, no account 4. clone and load Kronos-small. 24.7M params, it runs on a normal laptop, no GPU 5. feed it the last 512 candles and ask for the next 24, exactly like an LLM finishing a sentence 6. sample 100 futures, not one guess, and draw all of them right on the chart. the spread shows how risky the next move really is 7. read the regime: most paths pointing one way means TRENDING, paths scattered both ways means CHOPPY 8. backtest it walk-forward with real fees and paper trade it before you trust a single path i won't say anything more:

Сarm1ne

50,693 görüntüleme • 20 gün önce

8 BOTS JUST REVERSE-ENGINEERED A $400K/YR SAAS IN ONE NIGHT. watch the clip. that ring of 8 grok bots around the rea core is one closed app being torn apart in real time. trace, xref, read, site, spec, build, test, review. by the end of the loop the screen shows: - 2,418 files parsed - 23 blind calls - 16 pieces of evidence, 6 open assumptions - 9 modules reconstructed, 1 confirmed - 214 out of 214 observed behaviors matched that is not a stylised dashboard. it is literally the rea workflow: app → rea → grok bot → spec.md → build → test the numbers behind the hype are insane: - rea repo: 11k to 200k github stars in 5 days, global rank #161 - aegis authenticator: 3,077 classes, 133 test cases matched - dx-ball 1996: sound-panning function recovered, 3,205 behavioral tests passed - a steam game fully decompiled into unity in under 30 minutes - cost to understand a closed app: $0 and one evening the opportunity is wilder. pentest shops charge $8k to $50k per audit. reverse engineers bill $200 an hour and wait weeks. one mcp server + a bot with its own computer runs the same investigation while you sleep. one operator + grok bot + rea + one night = a reverse engineering firm. save the post, watch the terminal, then open the breakdown below.
1:12

8 BOTS JUST REVERSE-ENGINEERED A $400K/YR SAAS IN ONE NIGHT. watch the clip. that ring of 8 grok bots around the rea core is one closed app being torn apart in real time. trace, xref, read, site, spec, build, test, review. by the end of the loop the screen shows: - 2,418 files parsed - 23 blind calls - 16 pieces of evidence, 6 open assumptions - 9 modules reconstructed, 1 confirmed - 214 out of 214 observed behaviors matched that is not a stylised dashboard. it is literally the rea workflow: app → rea → grok bot → spec.md → build → test the numbers behind the hype are insane: - rea repo: 11k to 200k github stars in 5 days, global rank #161 - aegis authenticator: 3,077 classes, 133 test cases matched - dx-ball 1996: sound-panning function recovered, 3,205 behavioral tests passed - a steam game fully decompiled into unity in under 30 minutes - cost to understand a closed app: $0 and one evening the opportunity is wilder. pentest shops charge $8k to $50k per audit. reverse engineers bill $200 an hour and wait weeks. one mcp server + a bot with its own computer runs the same investigation while you sleep. one operator + grok bot + rea + one night = a reverse engineering firm. save the post, watch the terminal, then open the breakdown below.

shmidt

15,024 görüntüleme • 26 gün önce

Hermes Agent now has an official plugin for Reverse Engineer Anything by morluto ! I made a short video breaking down the plugin and showing how it works hermes plugins install rea That one command will get you set up with the proper MCP config and a special skill your agent can use!
4:26

Hermes Agent now has an official plugin for Reverse Engineer Anything by morluto ! I made a short video breaking down the plugin and showing how it works hermes plugins install rea That one command will get you set up with the proper MCP config and a special skill your agent can use!

tonbi

48,187 görüntüleme • 25 gün önce

Introducing Eleven: reverse engineering with your agent. i've always wanted to open any app and just ask what a function does, instead of staring at assembly for hours. so i built it with Eleven you can: → open Mac apps, Android APKs, Windows and Linux binaries, and read every function as pseudocode, assembly, a graph or hex → ask Claude, Codex, Gemini, Cursor or any ACP agent about the code. it reads the binary with you and you watch every step → your agent renames functions and leaves notes as suggestions. you accept or skip, and everything can be undone → patch bytes safely (always a copy, never the original), compare two builds, and debug with lldb free and open source
0:49

Introducing Eleven: reverse engineering with your agent. i've always wanted to open any app and just ask what a function does, instead of staring at assembly for hours. so i built it with Eleven you can: → open Mac apps, Android APKs, Windows and Linux binaries, and read every function as pseudocode, assembly, a graph or hex → ask Claude, Codex, Gemini, Cursor or any ACP agent about the code. it reads the binary with you and you watch every step → your agent renames functions and leaves notes as suggestions. you accept or skip, and everything can be undone → patch bytes safely (always a copy, never the original), compare two builds, and debug with lldb free and open source

Chizi

86,294 görüntüleme • 27 gün önce

this is where REA × Kimi K3 starts to look like cheating. reverse engineering usually means slowly tracing functions REA flips that process. the workflow becomes: find a function → collect evidence → infer behavior → cross-check it → connect it back to the system instead of: one model trying to understand the whole app it turns the codebase into hundreds of smaller investigations and sends 300 K3 agents across them in parallel. so while one group is tracing a function, others are already checking its callers, dependencies, behavior and evidence. and every new finding makes the map more complete. hundreds of agents are reconstructing different parts of it at the same time. full REA × Kimi K3 course below ↓
0:39

this is where REA × Kimi K3 starts to look like cheating. reverse engineering usually means slowly tracing functions REA flips that process. the workflow becomes: find a function → collect evidence → infer behavior → cross-check it → connect it back to the system instead of: one model trying to understand the whole app it turns the codebase into hundreds of smaller investigations and sends 300 K3 agents across them in parallel. so while one group is tracing a function, others are already checking its callers, dependencies, behavior and evidence. and every new finding makes the map more complete. hundreds of agents are reconstructing different parts of it at the same time. full REA × Kimi K3 course below ↓

Ricker

11,012 görüntüleme • 13 gün önce

claude + REA can rebuild software features without copying a single line of code opus 5.5 reads what REA finds inside a program, then rebuilds the feature in a separate clean-room setup. here's how to do it: 1. run npx rea-agents setup to connect REA to Claude Code 2. pick a feature and let REA figure out how it works. save the behavior and rules in a spec file 3. start a fresh Claude session with only that spec. rebuild the feature without touching the original code 4. use /goal to run the tests and check 3 intentionally broken versions. all 3 must fail one project recovered 697 functions in just 12 days, with 696 exact matches. the real trick is building tests that catch mistakes before they become part of the finished software.
0:25

claude + REA can rebuild software features without copying a single line of code opus 5.5 reads what REA finds inside a program, then rebuilds the feature in a separate clean-room setup. here's how to do it: 1. run npx rea-agents setup to connect REA to Claude Code 2. pick a feature and let REA figure out how it works. save the behavior and rules in a spec file 3. start a fresh Claude session with only that spec. rebuild the feature without touching the original code 4. use /goal to run the tests and check 3 intentionally broken versions. all 3 must fail one project recovered 697 functions in just 12 days, with 696 exact matches. the real trick is building tests that catch mistakes before they become part of the finished software.

Gipp 🦅

142,145 görüntüleme • 25 gün önce

this is where REA × Kimi K3 starts to get dangerous. reverse engineering usually forces one model to keep too much of the app in context at once. REA changes the shape of the problem first. so the workflow becomes less like “read this codebase” and more like distributed forensics: map the surface → assign narrow investigations → trace relationships → compare findings → reconstruct the architecture the important part is that no single agent needs to understand the whole app. the swarm builds that understanding collectively. that’s what makes REA × K3 interesting to me: reverse engineering stops being limited by how much code one model can hold in its head. full course in the article below ↓
0:35

this is where REA × Kimi K3 starts to get dangerous. reverse engineering usually forces one model to keep too much of the app in context at once. REA changes the shape of the problem first. so the workflow becomes less like “read this codebase” and more like distributed forensics: map the surface → assign narrow investigations → trace relationships → compare findings → reconstruct the architecture the important part is that no single agent needs to understand the whole app. the swarm builds that understanding collectively. that’s what makes REA × K3 interesting to me: reverse engineering stops being limited by how much code one model can hold in its head. full course in the article below ↓

Ricker

51,218 görüntüleme • 23 gün önce

OCTOBER’S MOST TRENDING GITHUB REPO: REA (Reverse Engineer Anything). 86.7K ⭐️ on GitHub, +25K just today. It lets your AI agent take apart almost any app and tell you how it works. Free and open source. Here’s the idea: You see a feature you like in some app. You ask your agent “how did they build this?” It digs into the app and explains it to you, with proof, without needing the source code. What it can open: → Mac, Linux and Windows apps → JavaScript and Electron apps → Android apps and websites → Everything runs on your computer, nothing gets uploaded → Works with Claude Code, Codex, Cursor, Gemini CLI and OpenCode Try something like: “Figure out how Discord shows who’s typing in real time, show me the proof, and build something similar for my project.” Heads up: it won’t give you the app’s original code or clone it. And knowing how something works doesn’t mean you’re allowed to copy it. How I’d use it: see how another tool solves a problem I have in my own app, find out which APIs it uses… the rest is up to your imagination. share this if you found it useful ♻️ and save it before you lose it 🔖 Repo ↓
17:37

OCTOBER’S MOST TRENDING GITHUB REPO: REA (Reverse Engineer Anything). 86.7K ⭐️ on GitHub, +25K just today. It lets your AI agent take apart almost any app and tell you how it works. Free and open source. Here’s the idea: You see a feature you like in some app. You ask your agent “how did they build this?” It digs into the app and explains it to you, with proof, without needing the source code. What it can open: → Mac, Linux and Windows apps → JavaScript and Electron apps → Android apps and websites → Everything runs on your computer, nothing gets uploaded → Works with Claude Code, Codex, Cursor, Gemini CLI and OpenCode Try something like: “Figure out how Discord shows who’s typing in real time, show me the proof, and build something similar for my project.” Heads up: it won’t give you the app’s original code or clone it. And knowing how something works doesn’t mean you’re allowed to copy it. How I’d use it: see how another tool solves a problem I have in my own app, find out which APIs it uses… the rest is up to your imagination. share this if you found it useful ♻️ and save it before you lose it 🔖 Repo ↓

céline ✧

50,644 görüntüleme • 29 gün önce

this is where REA × Kimi K3 starts to feel dangerous. reverse engineering normally means one model slowly reading through an app and trying to keep the whole architecture in context. REA changes that first. it breaks the app into smaller pieces that can be investigated separately - functions, dependencies, call paths, state changes, UI behavior. then K3 sends 300 agents across that map at the same time. so instead of: one model → one codebase → one long chain of reasoning you get: one app → hundreds of narrow investigations → one reconstructed system the swarm builds the understanding collectively. that’s what makes REA × K3 powerful: reverse engineering stops being limited by how much of the app one model can hold in context. full course in the article below ↓
0:40

this is where REA × Kimi K3 starts to feel dangerous. reverse engineering normally means one model slowly reading through an app and trying to keep the whole architecture in context. REA changes that first. it breaks the app into smaller pieces that can be investigated separately - functions, dependencies, call paths, state changes, UI behavior. then K3 sends 300 agents across that map at the same time. so instead of: one model → one codebase → one long chain of reasoning you get: one app → hundreds of narrow investigations → one reconstructed system the swarm builds the understanding collectively. that’s what makes REA × K3 powerful: reverse engineering stops being limited by how much of the app one model can hold in context. full course in the article below ↓

Ricker

69,545 görüntüleme • 14 gün önce