Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

This GitHub repo lets your AI agent take apart any app here's a GitHub repo with over 300,000 stars called REA (Reverse Engineer Anything), and it changes how you learn from other software. REA is two things: a set of instructions for your AI agent, and an MCP server....

pro.glitch's profile picture

Professor Glitch

114,300 subscribers

19,500 Aufrufe • vor 22 Tagen •via TikTok

BildungWissenschaft & Technologie#aiagents#claudecode#mcp#reverseengineering
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

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 Aufrufe • vor 23 Tagen

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 Aufrufe • vor 1 Monat

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 Aufrufe • vor 21 Tagen

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 Aufrufe • vor 28 Tagen

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 Aufrufe • vor 19 Tagen

MCP explained in one drawing: how your AI gets inside your apps (Claude, n8n, Gmail) Here's how your AI actually gets inside your apps. It's called MCP, and it fits in one drawing. On its own, an AI is a brain in a box. It can talk and think, but it can't open your email or build anything in n8n. It has no hands. 1. The door is the API. Most apps have a door for other software: Gmail has one, GitHub has one, n8n has one. Every door is a different shape, with its own rules and its own key. 2. The plug is MCP. It's one standard shape. On one side is the AI. On the other side is a small program called an MCP server, one per app, and it knows that app's door. The AI plugs in, and the server does the walking through the door. 3. The menu is the list of tools. When the AI plugs in, it sees every tool the app offers, in plain words. Gmail's server offers create a draft, search mail and read a message. n8n's server offers list workflows, create a workflow and test it. The AI reads the list like a menu, picks a tool and calls it. That's how Claude builds a whole workflow inside n8n, node by node, and checks its own work, while you never open n8n. 4. Connecting one takes one sentence. In Claude Code, say: "Connect yourself to my n8n, here's the address and a key I made just for you." Claude writes a small settings file with the server's name and the key. Type /mcp and it says connected. That's the setup for most apps. Some, like Gmail, you just sign in to instead. 5. The key is the important part. An MCP server can only use the tools on its menu, and only as far as its key allows. So make a key that can do the job and nothing more. If the app lets you limit a key, make it read only when reading is all you need. If it doesn't, use a test account. And if a key ever leaks, cancel it inside the app. One click, and nobody can use it, the AI included. One honest line: MCP doesn't make the AI smarter. It gives a smart thing a way to act, and everything it does through that plug, it does as you. So you still check the work, like you would a new hire's. If you're starting from scratch, I have step-by-step lessons for all of this inside my community. There are eight courses, in order, from the basics of AI to automations, building websites and apps, and AI agents. If you're interested, the link is in my profile. #mcp #cli ##aiagents #aiautomation #claudecode
2:56

MCP explained in one drawing: how your AI gets inside your apps (Claude, n8n, Gmail) Here's how your AI actually gets inside your apps. It's called MCP, and it fits in one drawing. On its own, an AI is a brain in a box. It can talk and think, but it can't open your email or build anything in n8n. It has no hands. 1. The door is the API. Most apps have a door for other software: Gmail has one, GitHub has one, n8n has one. Every door is a different shape, with its own rules and its own key. 2. The plug is MCP. It's one standard shape. On one side is the AI. On the other side is a small program called an MCP server, one per app, and it knows that app's door. The AI plugs in, and the server does the walking through the door. 3. The menu is the list of tools. When the AI plugs in, it sees every tool the app offers, in plain words. Gmail's server offers create a draft, search mail and read a message. n8n's server offers list workflows, create a workflow and test it. The AI reads the list like a menu, picks a tool and calls it. That's how Claude builds a whole workflow inside n8n, node by node, and checks its own work, while you never open n8n. 4. Connecting one takes one sentence. In Claude Code, say: "Connect yourself to my n8n, here's the address and a key I made just for you." Claude writes a small settings file with the server's name and the key. Type /mcp and it says connected. That's the setup for most apps. Some, like Gmail, you just sign in to instead. 5. The key is the important part. An MCP server can only use the tools on its menu, and only as far as its key allows. So make a key that can do the job and nothing more. If the app lets you limit a key, make it read only when reading is all you need. If it doesn't, use a test account. And if a key ever leaks, cancel it inside the app. One click, and nobody can use it, the AI included. One honest line: MCP doesn't make the AI smarter. It gives a smart thing a way to act, and everything it does through that plug, it does as you. So you still check the work, like you would a new hire's. If you're starting from scratch, I have step-by-step lessons for all of this inside my community. There are eight courses, in order, from the basics of AI to automations, building websites and apps, and AI agents. If you're interested, the link is in my profile. #mcp #cli ##aiagents #aiautomation #claudecode

Professor Glitch

18,500 Aufrufe • vor 27 Tagen

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 Aufrufe • vor 1 Monat

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 Aufrufe • vor 29 Tagen

Today we're launching Jitsu MCP. This is an MCP server that lets your agent run your entire event pipeline directly in Claude Code, Claude Desktop, Cursor, or VS Code. Here's how it works: Add the server: claude mcp add --transport http jitsu Run this prompt: "Route my web stream into ClickHouse, but only purchase and signup events. Send a test event, check Live Events, and if anything errors, find the function in the path and fix it." Approve the OAuth prompt once, and all 26 tools are live Your agent wires the streams, watches Live Events, and rewrites a function when one of them throws. It runs the fix against a real event before shipping it, so nothing is persisted until it works. Every change lands in the audit log tagged mcp, so you can tell what the agent did from what a person did. It's all MIT licensed, and it runs against your own deployment. Jitsu is one of the fastest growing open-source CDPs with 5,000+ GitHub stars. Capturing events is unlimited and free, and delivery is free up to 200k events a month. Comment Jitsu and I'll DM you the exact prompts I run in Claude Code to build an event pipeline end to end.
0:51

Today we're launching Jitsu MCP. This is an MCP server that lets your agent run your entire event pipeline directly in Claude Code, Claude Desktop, Cursor, or VS Code. Here's how it works: Add the server: claude mcp add --transport http jitsu Run this prompt: "Route my web stream into ClickHouse, but only purchase and signup events. Send a test event, check Live Events, and if anything errors, find the function in the path and fix it." Approve the OAuth prompt once, and all 26 tools are live Your agent wires the streams, watches Live Events, and rewrites a function when one of them throws. It runs the fix against a real event before shipping it, so nothing is persisted until it works. Every change lands in the audit log tagged mcp, so you can tell what the agent did from what a person did. It's all MIT licensed, and it runs against your own deployment. Jitsu is one of the fastest growing open-source CDPs with 5,000+ GitHub stars. Capturing events is unlimited and free, and delivery is free up to 200k events a month. Comment Jitsu and I'll DM you the exact prompts I run in Claude Code to build an event pipeline end to end.

Soham Mehta

283,165 Aufrufe • vor 2 Monaten

Holy sh*t... the AI skill Reverse Engineer Anything is INSANE. This GitHub repo lets your AI agent reverse engineer almost anything, understand exactly how it works, and build its own version from scratch. Even without the source code. It just hit 126K GitHub stars and is #1 trending right now. This feels illegal lol.
0:30

Holy sh*t... the AI skill Reverse Engineer Anything is INSANE. This GitHub repo lets your AI agent reverse engineer almost anything, understand exactly how it works, and build its own version from scratch. Even without the source code. It just hit 126K GitHub stars and is #1 trending right now. This feels illegal lol.

Brandon Chin

20,266 Aufrufe • vor 1 Monat

OpenAI, Anthropic and Microsoft all back the same standard for running apps inside AI chats. Booking .com, Figma, and Canva are already using it. Still, most developers have never heard of it. It's called MCP Apps. So, why does it matter? The next time someone buys from your website, they may never visit it. They'll ask ChatGPT or Claude, and the model decides how your product shows up. Usually as plain text, sometimes wrong, with none of the experience you built. That's the next shift in how people find you: - SEO was about Google finding your page. - AEO was about AI citing you. - MCP Apps are about your actual product showing up inside the chat. An MCP server returns data. An MCP App returns data plus an interactive UI, like hotel cards or an add-to-cart flow, right inside the chat. The model even knows what the user clicked. In this episode, we build an MCP app from start to finish with Julien, the lead maintainer of Skybridge, an open-source framework that lets you turn any React app into an MCP app. Chapters: 0:00 - Intro 2:44 - MCP servers vs MCP Apps 5:12 - Live demo: Booking .com in ChatGPT 9:24 - How MCP Apps work: context and shared state 15:43 - Skybridge and its devtools 17:48 - Live demo: an e-commerce app in ChatGPT 24:49 - Code walkthrough: MCP tools to React views 28:10 - Syncing UI state: "What's in my cart?" 32:16 - Agent skill to turn any React app → MCP App 37:52 - Outro Link to Skybridge GitHub repo: MCP Apps bring your website into the chat. WebMCP does the reverse and lets AI agents use your website through tools it exposes. I've also written a full article on it, quoted below.
40:22

OpenAI, Anthropic and Microsoft all back the same standard for running apps inside AI chats. Booking .com, Figma, and Canva are already using it. Still, most developers have never heard of it. It's called MCP Apps. So, why does it matter? The next time someone buys from your website, they may never visit it. They'll ask ChatGPT or Claude, and the model decides how your product shows up. Usually as plain text, sometimes wrong, with none of the experience you built. That's the next shift in how people find you: - SEO was about Google finding your page. - AEO was about AI citing you. - MCP Apps are about your actual product showing up inside the chat. An MCP server returns data. An MCP App returns data plus an interactive UI, like hotel cards or an add-to-cart flow, right inside the chat. The model even knows what the user clicked. In this episode, we build an MCP app from start to finish with Julien, the lead maintainer of Skybridge, an open-source framework that lets you turn any React app into an MCP app. Chapters: 0:00 - Intro 2:44 - MCP servers vs MCP Apps 5:12 - Live demo: Booking .com in ChatGPT 9:24 - How MCP Apps work: context and shared state 15:43 - Skybridge and its devtools 17:48 - Live demo: an e-commerce app in ChatGPT 24:49 - Code walkthrough: MCP tools to React views 28:10 - Syncing UI state: "What's in my cart?" 32:16 - Agent skill to turn any React app → MCP App 37:52 - Outro Link to Skybridge GitHub repo: MCP Apps bring your website into the chat. WebMCP does the reverse and lets AI agents use your website through tools it exposes. I've also written a full article on it, quoted below.

Akshay 🚀

18,064 Aufrufe • vor 1 Monat

🚨 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 Aufrufe • vor 22 Tagen

Opus 5.5 makes this AI stack look f…cking illegal 10 GitHub repos for building everything around the model 01 zen-mcp-server ▸ → your agent debates Gemini, GPT and local models mid-task 02 claude-context ▸ → semantic code search so the agent stops grepping blind 03 wshobson/agents ▸ → a roster of subagents, each with one narrow job 04 mcp-agent ▸ → workflow patterns built around MCP tools, not around chat 05 Backlog.md ▸ → tasks live in git, so the agent and you read the same board 06 Claude Code Development Kit ▸ → hooks, subagents and MCP wired for context at scale 07 agent-rules ▸ → shared guardrails the agent inherits in every repo 08 Agent Skills ▸ → one file that teaches the agent a job, portable across tools 09 agent-scan ▸ → scans your agents, MCP servers and skills for what leaks 10 awesome-claude-code-toolkit ▸ → the map: agents, skills, commands, hooks, MCP configs the architecture: rules → context → subagents → tools → state → review → scan I'd split the stack like this: context: claude-context → Development Kit work: wshobson/agents → mcp-agent → zen-mcp-server state: Backlog.md safety: agent-rules → Agent Skills → agent-scan everyone posts the SDK and the CLI the layer that decides whether your agent survives a week is this one the model is one folder in the stack ⭣
0:24

Opus 5.5 makes this AI stack look f…cking illegal 10 GitHub repos for building everything around the model 01 zen-mcp-server ▸ → your agent debates Gemini, GPT and local models mid-task 02 claude-context ▸ → semantic code search so the agent stops grepping blind 03 wshobson/agents ▸ → a roster of subagents, each with one narrow job 04 mcp-agent ▸ → workflow patterns built around MCP tools, not around chat 05 Backlog.md ▸ → tasks live in git, so the agent and you read the same board 06 Claude Code Development Kit ▸ → hooks, subagents and MCP wired for context at scale 07 agent-rules ▸ → shared guardrails the agent inherits in every repo 08 Agent Skills ▸ → one file that teaches the agent a job, portable across tools 09 agent-scan ▸ → scans your agents, MCP servers and skills for what leaks 10 awesome-claude-code-toolkit ▸ → the map: agents, skills, commands, hooks, MCP configs the architecture: rules → context → subagents → tools → state → review → scan I'd split the stack like this: context: claude-context → Development Kit work: wshobson/agents → mcp-agent → zen-mcp-server state: Backlog.md safety: agent-rules → Agent Skills → agent-scan everyone posts the SDK and the CLI the layer that decides whether your agent survives a week is this one the model is one folder in the stack ⭣

rody

18,089 Aufrufe • vor 1 Monat

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

43,062 Aufrufe • vor 12 Tagen

Someone built a free open source tool that lets your AI agent make polished screen recordings, so you can get a product demo video from one prompt. You ask your agent something like "make a video showing how human handoff works." It then: → Explores your site or desktop app and writes the scenario → Films it with a smooth cursor, auto zooms, callouts, captions and an optional voice-over → Gives you an MP4, and works with Claude Code, Codex, Cursor or any MCP client It has no AI of its own and needs no model key, because your agent does the thinking. README read, not run.
0:23

Someone built a free open source tool that lets your AI agent make polished screen recordings, so you can get a product demo video from one prompt. You ask your agent something like "make a video showing how human handoff works." It then: → Explores your site or desktop app and writes the scenario → Films it with a smooth cursor, auto zooms, callouts, captions and an optional voice-over → Gives you an MP4, and works with Claude Code, Codex, Cursor or any MCP client It has no AI of its own and needs no model key, because your agent does the thinking. README read, not run.

0xMarioNawfal

44,262 Aufrufe • vor 9 Tagen

Can your agent finally edit your videos? Yup, it's a repo called video use, by Browser Use. You put the raw footage in a folder. Then Claude Code or Codex edits it. It removes the filler words, cuts the dead space, adds the subtitles, and renders the file. Then it checks its own cut points. Most creators use the same small set of edits in every video. That style stays in your head and in your hands. This repo puts it in a file that an agent can read. People ask for a full YouTube channel on day one. They see bad results, and they stop. Start with one format instead. - One founder loom into a 60 second launch video - 3 clips out of one podcast recording Then make the format a system. Then you operate the system, or you sell it. - Real estate agents need listing videos - Coaches need clips - Agencies need ad variations Manual installation with git clone is possible. For 95% of people, the agent is faster. Here's how i intalled it: - Gave the setup prompt to Claude Code with shell access - Let it read install.md - Installed the repo - Connected FFmpeg - Registered the skill
4:22

Can your agent finally edit your videos? Yup, it's a repo called video use, by Browser Use. You put the raw footage in a folder. Then Claude Code or Codex edits it. It removes the filler words, cuts the dead space, adds the subtitles, and renders the file. Then it checks its own cut points. Most creators use the same small set of edits in every video. That style stays in your head and in your hands. This repo puts it in a file that an agent can read. People ask for a full YouTube channel on day one. They see bad results, and they stop. Start with one format instead. - One founder loom into a 60 second launch video - 3 clips out of one podcast recording Then make the format a system. Then you operate the system, or you sell it. - Real estate agents need listing videos - Coaches need clips - Agencies need ad variations Manual installation with git clone is possible. For 95% of people, the agent is faster. Here's how i intalled it: - Gave the setup prompt to Claude Code with shell access - Let it read install.md - Installed the repo - Connected FFmpeg - Registered the skill

The Startup Ideas Podcast (SIP) 🧃

15,605 Aufrufe • vor 2 Monaten

this github repo contains 50 of the most essential MCP servers that give your AI agents superpowers. > works with claude code, gemini, codex, cursor, and other MCP-compatible clients > MIT licensed > 5 categories, 50 MCP servers in total whether you want your agent to browse the web, manage files, interact with apps, or automate workflows, you'll find the right MCP here. link:
0:43

this github repo contains 50 of the most essential MCP servers that give your AI agents superpowers. > works with claude code, gemini, codex, cursor, and other MCP-compatible clients > MIT licensed > 5 categories, 50 MCP servers in total whether you want your agent to browse the web, manage files, interact with apps, or automate workflows, you'll find the right MCP here. link:

m0h

60,642 Aufrufe • vor 5 Monaten

What is a software factory? It is your workflow, your skills, and your domain knowledge, saved in files that the agent reads so the whole process is productized Think about the last app you built. You typed what you wanted, and the agent built it. You did not like it, so you made changes. You shipped it to Vercel, or you kept going. A factory puts structure on each of those steps. At each step you ask how to get the most from the model, and how to move faster. That is the conveyor belt. You ship quickly, and the quality stays the same. Mine is 5 md files. It works in Codex, Claude Code, and Cursor, because it does not depend on the model or the tool. Build your own.
3:06

What is a software factory? It is your workflow, your skills, and your domain knowledge, saved in files that the agent reads so the whole process is productized Think about the last app you built. You typed what you wanted, and the agent built it. You did not like it, so you made changes. You shipped it to Vercel, or you kept going. A factory puts structure on each of those steps. At each step you ask how to get the most from the model, and how to move faster. That is the conveyor belt. You ship quickly, and the quality stays the same. Mine is 5 md files. It works in Codex, Claude Code, and Cursor, because it does not depend on the model or the tool. Build your own.

The Startup Ideas Podcast (SIP) 🧃

17,326 Aufrufe • vor 1 Monat

INSANE: Grok 3 + Lovable = BEST AI Agent Apps!!!! Grok 3 generated the code for an AI agent that manages your Gmail - send, reply, and draft effortlessly Here's how it works: - Connect with your Gmail using Composio - Use Lovable to build an extremely cool frontend for the Agent - Agentic workflow with LlamaIndex Built with LlamaIndex 🦙 To connect your agents with more tools like Gmail, use
1:09

INSANE: Grok 3 + Lovable = BEST AI Agent Apps!!!! Grok 3 generated the code for an AI agent that manages your Gmail - send, reply, and draft effortlessly Here's how it works: - Connect with your Gmail using Composio - Use Lovable to build an extremely cool frontend for the Agent - Agentic workflow with LlamaIndex Built with LlamaIndex 🦙 To connect your agents with more tools like Gmail, use

Karan Vaidya

62,030 Aufrufe • vor 1 Jahr

Introducing Sarvam Voice Agents MCP. Describe the voice agent you want, and your coding tool builds it. The MCP connects your coding tool to Sarvam, so you can create agents, run campaigns, and analyse calls from the environment you already code in. Watch Sarvam Voice Agents MCP build a voice agent, call a list of people and report back. Build your first voice agent with the MCP:
2:48

Introducing Sarvam Voice Agents MCP. Describe the voice agent you want, and your coding tool builds it. The MCP connects your coding tool to Sarvam, so you can create agents, run campaigns, and analyse calls from the environment you already code in. Watch Sarvam Voice Agents MCP build a voice agent, call a list of people and report back. Build your first voice agent with the MCP:

Sarvam

20,218 Aufrufe • vor 29 Tagen