Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

this is getting really dangerous... REA creator posted 20 GitHub repos to build a whole 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 Pro...

cabbitar's profile picture

cabbit

1,293 subscribers

65,315 görüntüleme • 8 gün önce •via X (Twitter)

Bilim & Teknoloji
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

holy f*ck, someone put an entire reverse engineering degree on GitHub for free 7 repos, 560k+ stars in the right order they take you from a raw binary to agents that reverse engineer anything 1. Ghidra -> how to read any binary ↳ the NSA’s software reverse engineering framework, where everyone starts 2. radare2 -> the same skill in the terminal ↳ a UNIX-like reverse engineering framework and command-line toolset 3. LLM4Decompile -> an LLM that decompiles ↳ turns binary code into readable C, and the 9B v2 model reaches 64.9% re-executability on its own benchmark 4. r2ai -> an LLM inside radare2 ↳ LLM-based reversing for radare2, the moment AI starts reading the binary with you 5. ida-pro-mcp -> let the agent drive the tool ↳ bridges IDA Pro to language models through MCP 6. reverse-engineering-assistant -> the same for Ghidra ↳ an MCP server for reverse engineering tasks in Ghidra 7. REA -> agents that reverse engineer anything ↳ 35 target types, from native binaries and APKs to firmware, websites and Electron apps, with every finding backed by evidence the full list of what REA can reverse engineer below ↓
0:18

holy f*ck, someone put an entire reverse engineering degree on GitHub for free 7 repos, 560k+ stars in the right order they take you from a raw binary to agents that reverse engineer anything 1. Ghidra -> how to read any binary ↳ the NSA’s software reverse engineering framework, where everyone starts 2. radare2 -> the same skill in the terminal ↳ a UNIX-like reverse engineering framework and command-line toolset 3. LLM4Decompile -> an LLM that decompiles ↳ turns binary code into readable C, and the 9B v2 model reaches 64.9% re-executability on its own benchmark 4. r2ai -> an LLM inside radare2 ↳ LLM-based reversing for radare2, the moment AI starts reading the binary with you 5. ida-pro-mcp -> let the agent drive the tool ↳ bridges IDA Pro to language models through MCP 6. reverse-engineering-assistant -> the same for Ghidra ↳ an MCP server for reverse engineering tasks in Ghidra 7. REA -> agents that reverse engineer anything ↳ 35 target types, from native binaries and APKs to firmware, websites and Electron apps, with every finding backed by evidence the full list of what REA can reverse engineer below ↓

Sammy

16,923 görüntüleme • 8 gün önce

holy f*ck, someone just dropped an entire reverse engineering degree on GitHub for free. Now you can build agents that can reverse engineer almost anything: 1. Ghidra How to read any binary. The NSA’s reverse engineering framework. Where almost everyone starts. 2. radare2 The same skill, but in the terminal. UNIX-style reverse engineering framework and command-line toolset. 3. LLM4Decompile An LLM that decompiles. Turns binary code into readable C. The 9B v2 model hits 64.9% re-executability on its own benchmark. 4. r2ai An LLM inside radare2. LLM-powered reversing for radare2. This is where AI starts reading the binary with you. 5. ida-pro-mcp Let the agent drive the tool. Bridges IDA Pro to language models through MCP. 6. reverse-engineering-assistant The same thing for Ghidra. An MCP server for reverse engineering tasks inside Ghidra. 7. REA Agents that reverse engineer anything. 35 target types: native binaries, APKs, firmware, websites, Electron apps, and more. Every finding is backed by evidence. Read the full REA guide below ↓
0:10

holy f*ck, someone just dropped an entire reverse engineering degree on GitHub for free. Now you can build agents that can reverse engineer almost anything: 1. Ghidra How to read any binary. The NSA’s reverse engineering framework. Where almost everyone starts. 2. radare2 The same skill, but in the terminal. UNIX-style reverse engineering framework and command-line toolset. 3. LLM4Decompile An LLM that decompiles. Turns binary code into readable C. The 9B v2 model hits 64.9% re-executability on its own benchmark. 4. r2ai An LLM inside radare2. LLM-powered reversing for radare2. This is where AI starts reading the binary with you. 5. ida-pro-mcp Let the agent drive the tool. Bridges IDA Pro to language models through MCP. 6. reverse-engineering-assistant The same thing for Ghidra. An MCP server for reverse engineering tasks inside Ghidra. 7. REA Agents that reverse engineer anything. 35 target types: native binaries, APKs, firmware, websites, Electron apps, and more. Every finding is backed by evidence. Read the full REA guide below ↓

cabbit

20,375 görüntüleme • 8 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 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 • 25 gün önce

ex-lead Anthropic engineer leaked a chip that runs any company 24/7 and it’s f**king unreal REA → OPUS 5.5 → SONNET 5.5 → FABLE 5.1 all combined into one system this is REA as a chip: 5 layers, 5 dies, 1 system. REA core in the middle, 4 Claude models around it one model plans, one does the work, one makes the hard calls, and REA reverse-engineers any business you point it at only one exists in the world, valued at $100,000+ save it, this is a whole company in the palm of your hand ↓
0:18

ex-lead Anthropic engineer leaked a chip that runs any company 24/7 and it’s f**king unreal REA → OPUS 5.5 → SONNET 5.5 → FABLE 5.1 all combined into one system this is REA as a chip: 5 layers, 5 dies, 1 system. REA core in the middle, 4 Claude models around it one model plans, one does the work, one makes the hard calls, and REA reverse-engineers any business you point it at only one exists in the world, valued at $100,000+ save it, this is a whole company in the palm of your hand ↓

Noisy

17,905 görüntüleme • 25 gün önce

THESE 2 FREE REPOS SHOULD HONESTLY BE ILLEGAL. ONE SENTENCE TO CLAUDE CODE, 60 SECONDS OF WATCHING, AND A DESKTOP TRADING CHART IS RUNNING ON 4 EXCHANGES IN YOUR TERMINAL FOR $0. they're called rea and ccxt. both open source. here's how it works: > rea reads 18,402 trades and finds how the app builds its footprint chart > it rebuilds it in 256 lines, 12 of 12 tests passed > ccxt feeds it binance, okx, bybit and coinbase at once here's how to run it: 1 → pip install ccxt 2 → plug rea into claude code 3 → ask it to rebuild one chart in your terminal honestly the spread line is the part i keep watching: buy coinbase, sell bybit, 11.3 bps. how the replay ends is on screen in the clip. i won't say anything more. bookmark this ↓
0:15

THESE 2 FREE REPOS SHOULD HONESTLY BE ILLEGAL. ONE SENTENCE TO CLAUDE CODE, 60 SECONDS OF WATCHING, AND A DESKTOP TRADING CHART IS RUNNING ON 4 EXCHANGES IN YOUR TERMINAL FOR $0. they're called rea and ccxt. both open source. here's how it works: > rea reads 18,402 trades and finds how the app builds its footprint chart > it rebuilds it in 256 lines, 12 of 12 tests passed > ccxt feeds it binance, okx, bybit and coinbase at once here's how to run it: 1 → pip install ccxt 2 → plug rea into claude code 3 → ask it to rebuild one chart in your terminal honestly the spread line is the part i keep watching: buy coinbase, sell bybit, 11.3 bps. how the replay ends is on screen in the clip. i won't say anything more. bookmark this ↓

RetroChainer

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

call me crazy but its pretty clear now. rea + jev is going to change more lives in 2026 than open source ever did. any app goes to rea. jev makes the calls. rea does the work. the app is yours. if this lands on your timeline dont scroll past it. send this to claude code. connect it to rea and jev. thats it. thank me later. most people will ignore this. the ones who dont will be fine. simple as that.
0:14

call me crazy but its pretty clear now. rea + jev is going to change more lives in 2026 than open source ever did. any app goes to rea. jev makes the calls. rea does the work. the app is yours. if this lands on your timeline dont scroll past it. send this to claude code. connect it to rea and jev. thats it. thank me later. most people will ignore this. the ones who dont will be fine. simple as that.

Archive

40,474 görüntüleme • 10 gün önce

This is f*cking insane, this GitHub repo + Opus 5.5 turns any Android phone into a hands-free agent An Android phone, reverse-engineered with Opus 5.5... 1 sentence out loud = the phone opens Telegram, finds the app and installs it by itself. No taps, no swipes, nobody touches the screen. here's the full guide step by step: step 1 → put the phone and a laptop on the same Wi-Fi step 2 → turn on wireless debugging on the phone: Settings → About phone → tap Build number 7 times → Developer options → Wireless debugging step 3 → paste the prompt below into Claude Code on Opus 5.5 with the GitHub repo and a screenshot of the phone's About screen step 4 → Opus reads the repo and finds the loophole: every Android phone takes orders over ADB on a home network. The same door developers use to test apps step 5 → it checks the phone first: model, Android version, installed apps, and saves a restore point so nothing breaks step 6 → it writes a tiny agent with exactly 3 tools: see the screen, tap, type. Nothing else step 7 → it plugs that agent into Claude Code as an MCP. Claude is the brain, the phone is the hands step 8 → press Allow on the phone once, the last tap ever needed. Then say "open Telegram and install ChatGPT" and watch it tap through by itself the result: you talk, the phone does it, hands stay in pockets... p.s: the repo works on 300+ Android models from 40 brands, no root needed Find GitHub repo + full prompt below Then read the full guide on reverse engineering with Opus 5.5 in the article.
0:17

This is f*cking insane, this GitHub repo + Opus 5.5 turns any Android phone into a hands-free agent An Android phone, reverse-engineered with Opus 5.5... 1 sentence out loud = the phone opens Telegram, finds the app and installs it by itself. No taps, no swipes, nobody touches the screen. here's the full guide step by step: step 1 → put the phone and a laptop on the same Wi-Fi step 2 → turn on wireless debugging on the phone: Settings → About phone → tap Build number 7 times → Developer options → Wireless debugging step 3 → paste the prompt below into Claude Code on Opus 5.5 with the GitHub repo and a screenshot of the phone's About screen step 4 → Opus reads the repo and finds the loophole: every Android phone takes orders over ADB on a home network. The same door developers use to test apps step 5 → it checks the phone first: model, Android version, installed apps, and saves a restore point so nothing breaks step 6 → it writes a tiny agent with exactly 3 tools: see the screen, tap, type. Nothing else step 7 → it plugs that agent into Claude Code as an MCP. Claude is the brain, the phone is the hands step 8 → press Allow on the phone once, the last tap ever needed. Then say "open Telegram and install ChatGPT" and watch it tap through by itself the result: you talk, the phone does it, hands stay in pockets... p.s: the repo works on 300+ Android models from 40 brands, no root needed Find GitHub repo + full prompt below Then read the full guide on reverse engineering with Opus 5.5 in the article.

NO1ennn

36,867 görüntüleme • 17 gün önce

19 devices on my Airbnb room Wi-Fi. Claude Code found the 1 that wasn't fine. Last month I reverse engineered apps. This month I reverse engineer Airbnb rooms. One prompt, 7 steps, read only the whole way: Wi-Fi: lists every device on the network, finds the maker by MAC and flags anything open on camera ports like 554 Behavior: a "smoke detector" that calls itself IPC-CAM on the network is not a smoke detector - devices tell on themselves Bluetooth: logs every tracker for 10 minutes, then again in the hallway - an AirTag that walks out with me is in my bag My phone: Amnesty's free MVT tool checks it for known stalkerware Host's app: if they make me install a check-in app, REA opens it and lists every tracker and permission inside Lenses: a flashlight sweep of everything that faces the bed and the shower Report: every finding marked fact, guess or unknown - with proof for each one: MAC, port or file Then I break it on purpose. I hide my own AirTag in the room and run it again. If it misses mine, I don't trust the green. It never logs into anything, never changes a setting, and tells me what it can't see - like a camera on its own SIM card. 20 minutes of checks beats 7 nights of wondering. I'll post the full case file on my profile soon. Save this post for your next trip and stay safe.
0:16

19 devices on my Airbnb room Wi-Fi. Claude Code found the 1 that wasn't fine. Last month I reverse engineered apps. This month I reverse engineer Airbnb rooms. One prompt, 7 steps, read only the whole way: Wi-Fi: lists every device on the network, finds the maker by MAC and flags anything open on camera ports like 554 Behavior: a "smoke detector" that calls itself IPC-CAM on the network is not a smoke detector - devices tell on themselves Bluetooth: logs every tracker for 10 minutes, then again in the hallway - an AirTag that walks out with me is in my bag My phone: Amnesty's free MVT tool checks it for known stalkerware Host's app: if they make me install a check-in app, REA opens it and lists every tracker and permission inside Lenses: a flashlight sweep of everything that faces the bed and the shower Report: every finding marked fact, guess or unknown - with proof for each one: MAC, port or file Then I break it on purpose. I hide my own AirTag in the room and run it again. If it misses mine, I don't trust the green. It never logs into anything, never changes a setting, and tells me what it can't see - like a camera on its own SIM card. 20 minutes of checks beats 7 nights of wondering. I'll post the full case file on my profile soon. Save this post for your next trip and stay safe.

RazeDen

17,757 görüntüleme • 16 gün önce

🚨 YOUR AI AGENT CAN NOW READ YOUR NOTIFICATIONS AND ACT ON THEM BEFORE YOU EVEN SEE THEM It’s called PhoneUse and it just launched. It gives your agent its own phone in the cloud, a real Android, connected to Claude through an MCP. Time needed: 10 minutes Steps: connect the MCP, tell your agent what to watch for What it handles on its own: → Your flight gets delayed: it sees the push notification and texts whoever is picking you up → Your Uber is on the way: it checks the driver’s status and lets people know when you’ll arrive → An app asks for a 2-step code: it reads the SMS and gets through the verification → An old app with no API: it opens it and taps through it like a person would Until now agents were stuck in the browser. Most of the apps we use every day don’t have an API, so they couldn’t touch them. Now they have a phone. Save it before it gets deleted 🔖 Link in the comments 👇
0:13

🚨 YOUR AI AGENT CAN NOW READ YOUR NOTIFICATIONS AND ACT ON THEM BEFORE YOU EVEN SEE THEM It’s called PhoneUse and it just launched. It gives your agent its own phone in the cloud, a real Android, connected to Claude through an MCP. Time needed: 10 minutes Steps: connect the MCP, tell your agent what to watch for What it handles on its own: → Your flight gets delayed: it sees the push notification and texts whoever is picking you up → Your Uber is on the way: it checks the driver’s status and lets people know when you’ll arrive → An app asks for a 2-step code: it reads the SMS and gets through the verification → An old app with no API: it opens it and taps through it like a person would Until now agents were stuck in the browser. Most of the apps we use every day don’t have an API, so they couldn’t touch them. Now they have a phone. Save it before it gets deleted 🔖 Link in the comments 👇

draven

38,752 görüntüleme • 19 gün önce

🚨 AI AGENTS COULD ALREADY USE COMPUTERS. NOW THEY HAVE THEIR OWN PHONE It’s called PhoneUse, and it launches today. You give your agent a cloud phone, a real Android or iPhone, tell it what to do, and it uses the phone just like you would. First came computer-use. Then browser-use. Now there’s phone-use. What it can do: → Order an Uber and text you updates along the way → Research trends on TikTok → Get around old apps with no API, like insurance apps → Complete two-factor verification → Read your notifications and act on its own: if your flight is delayed, it messages you And here’s the big part: most mobile apps have no API and no MCP. Until now, agents couldn’t get into them. With a phone, they can. It connects through MCP or an API, so you can use it from the agent you already have. The world still runs on mobile. Now your agent does too. Save this before you forget 🔖 Link in the comments 👇
0:20

🚨 AI AGENTS COULD ALREADY USE COMPUTERS. NOW THEY HAVE THEIR OWN PHONE It’s called PhoneUse, and it launches today. You give your agent a cloud phone, a real Android or iPhone, tell it what to do, and it uses the phone just like you would. First came computer-use. Then browser-use. Now there’s phone-use. What it can do: → Order an Uber and text you updates along the way → Research trends on TikTok → Get around old apps with no API, like insurance apps → Complete two-factor verification → Read your notifications and act on its own: if your flight is delayed, it messages you And here’s the big part: most mobile apps have no API and no MCP. Until now, agents couldn’t get into them. With a phone, they can. It connects through MCP or an API, so you can use it from the agent you already have. The world still runs on mobile. Now your agent does too. Save this before you forget 🔖 Link in the comments 👇

silvan

20,056 görüntüleme • 19 gün önce

After Andrej Karpathy released autoresearch, where an agent runs experiments in a loop on its own, I packed his method into one prompt that turns Opus 5.5 into a graph and can carry almost any task to the finish. → writes a check that can actually fail, first → splits the task into parts → runs the independent parts in parallel → loops each one until it passes the check → sends back only the part that failed → turns every mistake into a rule for next time → calls you only for the step that can’t be undone Throw it at Opus 5.5 with the task you’ve been putting off for a week, and you’ll see the difference in one run. The full prompt is in the comments. How to tune it for your own work is in the article below. Save it before it gets lost ↓
0:15

After Andrej Karpathy released autoresearch, where an agent runs experiments in a loop on its own, I packed his method into one prompt that turns Opus 5.5 into a graph and can carry almost any task to the finish. → writes a check that can actually fail, first → splits the task into parts → runs the independent parts in parallel → loops each one until it passes the check → sends back only the part that failed → turns every mistake into a rule for next time → calls you only for the step that can’t be undone Throw it at Opus 5.5 with the task you’ve been putting off for a week, and you’ll see the difference in one run. The full prompt is in the comments. How to tune it for your own work is in the article below. Save it before it gets lost ↓

Hoodie

326,615 görüntüleme • 6 gün önce

ANTHROPIC JUST TURNED AI AGENTS INTO GIT REPOS Anthropic shipped "ant" - a CLI that runs every Claude API endpoint straight from your terminal. The headline isn't the terminal access. It's that you can now version-control an AI agent as YAML in Git and have CI sync it to the Claude Platform, the same way you ship code. - Every API resource is a subcommand: messages, models, files, agents, sessions - Define an agent in a YAML file, check it into your repo, and keep it in sync with one update command - Spin up a session, send it an event, then pull every event and tool call back from the same CLI - Claude Code knows how to drive ant out of the box - it shells out and reads the results with no glue code Agents just stopped being prompts you babysit and became infrastructure you deploy.
0:18

ANTHROPIC JUST TURNED AI AGENTS INTO GIT REPOS Anthropic shipped "ant" - a CLI that runs every Claude API endpoint straight from your terminal. The headline isn't the terminal access. It's that you can now version-control an AI agent as YAML in Git and have CI sync it to the Claude Platform, the same way you ship code. - Every API resource is a subcommand: messages, models, files, agents, sessions - Define an agent in a YAML file, check it into your repo, and keep it in sync with one update command - Spin up a session, send it an event, then pull every event and tool call back from the same CLI - Claude Code knows how to drive ant out of the box - it shells out and reads the results with no glue code Agents just stopped being prompts you babysit and became infrastructure you deploy.

BuBBliK

200,690 görüntüleme • 5 ay önce

MOONSHOT JUST CLONED CLAUDE CODE AND MADE IT FREE. It's called Kimi Code CLI. Open source, MIT license, maintained by the lab that shipped K3 yesterday. And it does things Claude Code doesn't: → drop a screen recording into the chat as input → built-in coder, explore, and plan subagents, each in its own context → plan mode before it touches a single file → MCP servers configured by the agent itself via /mcp-config → plugs into Zed, JetBrains, and VS Code → one binary, no Node setup, starts in milliseconds The CLI costs $0. K3 behind it starts at $3 per million tokens. Grab it for free👇
0:17

MOONSHOT JUST CLONED CLAUDE CODE AND MADE IT FREE. It's called Kimi Code CLI. Open source, MIT license, maintained by the lab that shipped K3 yesterday. And it does things Claude Code doesn't: → drop a screen recording into the chat as input → built-in coder, explore, and plan subagents, each in its own context → plan mode before it touches a single file → MCP servers configured by the agent itself via /mcp-config → plugs into Zed, JetBrains, and VS Code → one binary, no Node setup, starts in milliseconds The CLI costs $0. K3 behind it starts at $3 per million tokens. Grab it for free👇

darkzodchi

408,234 görüntüleme • 3 ay önce

this AI engineering breakdown from IBM Technology is pure f*cking treasure it explains the role as a connected system 01 Python and APIs give you the surface to build on: services, data, integrations, and the software around the model 02 RAG and embeddings solve the context layer: finding the right information before the model has to reason about it 03 agents turn that context into work: they choose tools, run steps, and move toward an outcome 04 observability closes the feedback loop: traces, metrics, failures, latency, and the evidence needed to improve the system 05 deployment is where the system becomes real: reliability, constraints, and the conditions that let people actually depend on it the model sits inside this architecture the AI engineer connects every layer into one operating loop: build → retrieve → act → observe → ship save this, then build your solo business with an AI employee ⭣
0:18

this AI engineering breakdown from IBM Technology is pure f*cking treasure it explains the role as a connected system 01 Python and APIs give you the surface to build on: services, data, integrations, and the software around the model 02 RAG and embeddings solve the context layer: finding the right information before the model has to reason about it 03 agents turn that context into work: they choose tools, run steps, and move toward an outcome 04 observability closes the feedback loop: traces, metrics, failures, latency, and the evidence needed to improve the system 05 deployment is where the system becomes real: reliability, constraints, and the conditions that let people actually depend on it the model sits inside this architecture the AI engineer connects every layer into one operating loop: build → retrieve → act → observe → ship save this, then build your solo business with an AI employee ⭣

beamnxw ./

13,611 görüntüleme • 1 ay önce

Holy sh*t, this GitHub repo + Opus 5.5 turned my TV into Jarvis powered by Grok Bot I reverse-engineered my Android TV with Opus 5.5... 1 sentence out loud = Netflix opens and scrolls itself. No remote, no phone, no ads on the home screen. here's the full guide step by step: • step 1 → put your TV and your laptop on the same Wi-Fi • step 2 → turn on network debugging on the TV: Settings → About → tap Build 7 times → Developer options • step 3 → paste the prompt below into Claude Code on Opus 5.5 with the GitHub repo and a photo of your TV's About screen • step 4 → Opus reads the repo and finds the loophole: every Android TV takes orders over ADB on your home network. The same door the phone remote apps use • step 5 → it cleans the TV first: ads, tracking and brand bloat switched off, restore point saved, every app can come back • step 6 → it writes a tiny remote with exactly 3 tools: open Netflix, move, select. Nothing else • step 7 → it plugs that remote into Grok Bot as a plugin. Grok is the ears, the plugin is the hands • step 8 → press Allow on the TV once, the last time you touch the remote. Then say "Hey Grok, open Netflix" and watch it browse for you the result: you talk, the TV listens, and the home screen finally has zero ads... p.s: the repo covers 131 TV models from 46 brands Find gitHub repo + full prompt below Then read the full guide on reverse engineering with Opus 5.5 in the article.
0:15

Holy sh*t, this GitHub repo + Opus 5.5 turned my TV into Jarvis powered by Grok Bot I reverse-engineered my Android TV with Opus 5.5... 1 sentence out loud = Netflix opens and scrolls itself. No remote, no phone, no ads on the home screen. here's the full guide step by step: • step 1 → put your TV and your laptop on the same Wi-Fi • step 2 → turn on network debugging on the TV: Settings → About → tap Build 7 times → Developer options • step 3 → paste the prompt below into Claude Code on Opus 5.5 with the GitHub repo and a photo of your TV's About screen • step 4 → Opus reads the repo and finds the loophole: every Android TV takes orders over ADB on your home network. The same door the phone remote apps use • step 5 → it cleans the TV first: ads, tracking and brand bloat switched off, restore point saved, every app can come back • step 6 → it writes a tiny remote with exactly 3 tools: open Netflix, move, select. Nothing else • step 7 → it plugs that remote into Grok Bot as a plugin. Grok is the ears, the plugin is the hands • step 8 → press Allow on the TV once, the last time you touch the remote. Then say "Hey Grok, open Netflix" and watch it browse for you the result: you talk, the TV listens, and the home screen finally has zero ads... p.s: the repo covers 131 TV models from 46 brands Find gitHub repo + full prompt below Then read the full guide on reverse engineering with Opus 5.5 in the article.

Codez

44,528 görüntüleme • 17 gün önce

Opus 5.5 is f*cking insane at UI design 20 tools to build your own UI design studio with Opus 5.5 landing pages. dashboards. app screens. full design systems. collect the references, set the tokens, build the components, check every state, ship. 01 shadcn/ui ▸ copy components into your repo and own the code 02 Frontend Design skill ▸ push your agent past templated default layouts 03 Tailwind CSS ▸ style everything with utility classes the agent can read 04 Radix Primitives ▸ get accessible dialogs, menus and popovers out of the box 05 Motion ▸ add hover, press and layout micro-interactions 06 Magic UI ▸ drop in animated landing page components 07 Lucide ▸ keep every icon in one consistent style 08 Figma MCP ▸ hand your agent the real frame, variables and components 09 Mobbin ▸ study real app screens before you design (free tier) 10 Laws of UX ▸ ground layout decisions in proven principles 11 Google Fonts ▸ choose typefaces for headlines and readable body text 12 Fontshare ▸ get free display fonts that don't look like everyone else's 13 Realtime Colors ▸ preview your palette on a real page before committing 14 WebAIM Contrast Checker ▸ make sure your text actually passes contrast 15 Storybook ▸ build and review every component state in isolation 16 Playwright ▸ let the agent screenshot its own UI and fix what it sees 17 Chrome DevTools MCP ▸ let the agent inspect the live page, console and performance 18 Unsplash ▸ find free photos for heroes and mockups 19 Squoosh ▸ compress images before they slow the page down 20 Vercel ▸ ship a preview link for every change the loop: write the brief → collect references → set the tokens → build the components → design every state → screenshot and fix → ship start with one screen. make every element earn its place. save this, then read the full guide for Opus 5.5 UI Engineering ↓
0:20

Opus 5.5 is f*cking insane at UI design 20 tools to build your own UI design studio with Opus 5.5 landing pages. dashboards. app screens. full design systems. collect the references, set the tokens, build the components, check every state, ship. 01 shadcn/ui ▸ copy components into your repo and own the code 02 Frontend Design skill ▸ push your agent past templated default layouts 03 Tailwind CSS ▸ style everything with utility classes the agent can read 04 Radix Primitives ▸ get accessible dialogs, menus and popovers out of the box 05 Motion ▸ add hover, press and layout micro-interactions 06 Magic UI ▸ drop in animated landing page components 07 Lucide ▸ keep every icon in one consistent style 08 Figma MCP ▸ hand your agent the real frame, variables and components 09 Mobbin ▸ study real app screens before you design (free tier) 10 Laws of UX ▸ ground layout decisions in proven principles 11 Google Fonts ▸ choose typefaces for headlines and readable body text 12 Fontshare ▸ get free display fonts that don't look like everyone else's 13 Realtime Colors ▸ preview your palette on a real page before committing 14 WebAIM Contrast Checker ▸ make sure your text actually passes contrast 15 Storybook ▸ build and review every component state in isolation 16 Playwright ▸ let the agent screenshot its own UI and fix what it sees 17 Chrome DevTools MCP ▸ let the agent inspect the live page, console and performance 18 Unsplash ▸ find free photos for heroes and mockups 19 Squoosh ▸ compress images before they slow the page down 20 Vercel ▸ ship a preview link for every change the loop: write the brief → collect references → set the tokens → build the components → design every state → screenshot and fix → ship start with one screen. make every element earn its place. save this, then read the full guide for Opus 5.5 UI Engineering ↓

Asteri

11,443 görüntüleme • 24 gün önce

This is the most DANGEROUS thing on the internet right now 143k stars in 2 days and that says it all REA (Reverse Engineer Anything) this open-source MCP lets your AI agent deconstruct any app, all the way down to machine code I unlocked TradingView's full feature set using REA and got FREE access to their premium indicators. The software is ready to go How it works: 1. Direct REA to TradingView’s public web application to map out all core functionalities, including chart controls, technical indicators, and alert mechanisms 2. Observe and document system behavior when modifying symbols, adjusting timeframes, overlaying indicators, plotting chart levels, or saving custom dashboard layouts 3. Leverage REA’s suite of MCP tools to inspect accessible software artifacts and map underlying application workflows based on concrete evidence 4. Supply these technical insights to Claude Opus 5.5 to produce a comprehensive specification and an actionable implementation roadmap 5. Engineer an independent charting platform complete with live market feeds, candlestick rendering, technical analysis tools, drawing features, and saved watchlists 6. Integrate a quantitative strategy engine capable of backtesting against historical market data while accounting for trading fees, price slippage, and maximum drawdowns 7. Systematically test every subsystem against real-world and benchmarked behaviors, resolving bugs iteratively until the platform operates seamlessly 8. Deliver a fully custom, end-to-end TradingView-inspired quantitative research workstation built on fully owned, extensible source code This is worth a shot
0:15

This is the most DANGEROUS thing on the internet right now 143k stars in 2 days and that says it all REA (Reverse Engineer Anything) this open-source MCP lets your AI agent deconstruct any app, all the way down to machine code I unlocked TradingView's full feature set using REA and got FREE access to their premium indicators. The software is ready to go How it works: 1. Direct REA to TradingView’s public web application to map out all core functionalities, including chart controls, technical indicators, and alert mechanisms 2. Observe and document system behavior when modifying symbols, adjusting timeframes, overlaying indicators, plotting chart levels, or saving custom dashboard layouts 3. Leverage REA’s suite of MCP tools to inspect accessible software artifacts and map underlying application workflows based on concrete evidence 4. Supply these technical insights to Claude Opus 5.5 to produce a comprehensive specification and an actionable implementation roadmap 5. Engineer an independent charting platform complete with live market feeds, candlestick rendering, technical analysis tools, drawing features, and saved watchlists 6. Integrate a quantitative strategy engine capable of backtesting against historical market data while accounting for trading fees, price slippage, and maximum drawdowns 7. Systematically test every subsystem against real-world and benchmarked behaviors, resolving bugs iteratively until the platform operates seamlessly 8. Deliver a fully custom, end-to-end TradingView-inspired quantitative research workstation built on fully owned, extensible source code This is worth a shot

Bober_smart

36,598 görüntüleme • 29 gün önce

F*ck YES... Claude Opus 5.5 just reverse-engineered my home one prompt found every device on my Wi-Fi - now one chat runs them all try with yours, here's step by step guide: step 1 → copy prompt below and paste it into Claude Code on a computer on your home Wi-Fi step 2 → It scans your whole network and names everey device it finds, brand and model where it can step 3 → for each one it tells you what's wrong and what it can fix or improve step 4 → pick the devices to take over, it backs up each one first step 5 → passwords go into your keychain with one command, never into the chat step 6 + the result → say yes and Claude fixes your slow Wi-Fi, cuts ads and bloat on your TV, sets schedules on your AC and much more (every change has an undo) Change your life today. Then read article below on full reverse-engineering:
0:19

F*ck YES... Claude Opus 5.5 just reverse-engineered my home one prompt found every device on my Wi-Fi - now one chat runs them all try with yours, here's step by step guide: step 1 → copy prompt below and paste it into Claude Code on a computer on your home Wi-Fi step 2 → It scans your whole network and names everey device it finds, brand and model where it can step 3 → for each one it tells you what's wrong and what it can fix or improve step 4 → pick the devices to take over, it backs up each one first step 5 → passwords go into your keychain with one command, never into the chat step 6 + the result → say yes and Claude fixes your slow Wi-Fi, cuts ads and bloat on your TV, sets schedules on your AC and much more (every change has an undo) Change your life today. Then read article below on full reverse-engineering:

codila

30,731 görüntüleme • 19 gün önce