How to Reverse Engineer Anything Better Than 99% of People
This video explains how Reverse Engineer Anything (REA) lets Claude use tools such as Ghidra, Hopper, or IDA through MCP to investigate compiled applications and rebuild selected behavior. It teaches learners to distinguish inspectable local logic from inaccessible cloud services, test recreations against observed behavior, and begin with one useful feature rather than cloning an entire product.
Samin YasarWatchTranscript found
Quick learning frame
Read this before watching.
Agent ops treats agents like services: observable state, queues, permissions, logs, recovery, and post-run review.
New playlist item from Samin Yasar; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to scope a reverse-engineering project around an observable, locally executed feature while identifying the back-end behavior, data, and licensed source code that cannot simply be recovered.
Watch for the shift from claim to mechanism. The learning value is the point where the transcript reveals a repeatable action, tool boundary, context move, review habit, or artifact.
Concept diagram
Where this video fits.
01Project state
02Session
03Queue/Kanban
04Tools
05Logs
06Recovery
07Post-run review
Deep lesson
Turn this video into working knowledge.
3,968 cleaned transcript words reviewed across 1,116 timed caption segments.
Thesis
How to Reverse Engineer Anything Better Than 99% of People teaches a practical hermes operations move: This video explains how Reverse Engineer Anything (REA) lets Claude use tools such as Ghidra, Hopper, or IDA through MCP to investigate compiled applications and rebuild selected behavior. It teaches learners to distinguish inspectable local logic from inaccessible cloud services, test recreations against observed behavior, and begin with one useful feature rather than cloning an entire product.
The goal is not to remember the video. The goal is to extract the operating principle, tie it to timestamped evidence, test how far the claim transfers, and make something reusable.
0:00
Inspect Through Conversation
“This new open source repo called reverse engineer anything lets you reverse engineer applications and build your own versions that you can customize and even resell. So, for example, this is an Mac app that I probably would...”
REA does not invent reverse engineering; it exposes established tools such as Ghidra, Hopper, and IDA to Claude or ChatGPT through an MCP server. That lowers the barrier to asking targeted questions about compiled software, while open-source licenses separately determine how visible source may be used, changed, or shared. Choose learner-owned, open-source, or explicitly authorized software, check its license or terms, then write three prompts about one permitted feature: where it begins, what local code or data supports it, and how to test a recreation.
6:58
Know The Boundary
“talking from there. And it essentially act as my personal service. And if I'm using cloud code, code X, whatever, or Hermes, I can do it all from one place if I'm out and about, right? So, for...”
Decompilation can reveal clues about behavior but does not recover the developer's exact source, and local applications generally expose more than cloud-connected ones. REA may trace a generate button or its API request, but it cannot retrieve a private video model, back-end implementation, or the company's database, so those pieces need replacements or new implementations. For software you own or are permitted to inspect, map the front end, API, back end, database, and on-device logic, then mark what can be inspected and what would need a separate implementation.
16:31
Solve One Friction
“just put up with, but because of these open-source repos, now it's something you can understand, adapt, and actually build on for yourself or even for others. But, you know, if you have a mission, you can push...”
The demonstrated Vitals recreation works because its useful behavior runs on the Mac, making it a better candidate than a feature dependent on private cloud infrastructure. The recommended product approach is to start from a problem you personally have, study only the relevant pieces, add a distinctive missing feature, test it, and show it to someone with the same need. Choose an authorized or appropriately licensed app with one missing feature, confirm whether it runs locally, and define the smallest testable version allowed by its terms; recheck redistribution rights before sharing or selling it.
01
Project state
Start with this video's job: This video explains how Reverse Engineer Anything (REA) lets Claude use tools such as Ghidra, Hopper, or IDA through MCP to investigate compiled applications and rebuild selected behavior. It teaches learners to distinguish inspectable local logic from inaccessible cloud services, test recreations against observed behavior, and begin with one useful feature rather than cloning an entire product. Treat "Project state" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:00, where the video says: “This new open source repo called reverse engineer anything lets you reverse engineer applications and build your own versions that you can customize and even resell. So, for example, this is an Mac app that I probably would...”
02
Session
Use "Session" to locate the part of the hermes operations mechanism the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 6:58, where the video says: “talking from there. And it essentially act as my personal service. And if I'm using cloud code, code X, whatever, or Hermes, I can do it all from one place if I'm out and about, right? So, for...”
03
Queue/Kanban
Turn "Queue/Kanban" into the reusable artifact for this lesson: A Hermes-style agent-ops runbook with health checks, state transitions, logs, recovery steps, and review criteria. This is where watching becomes something you can inspect and reuse.
04
Tools
Use "Tools" as the application surface. Decide whether the idea touches a browser flow, a local file, a model choice, a source document, a UI, or a review step.
05
Logs
Use "Logs" to prove the lesson. The evidence should connect back to the video title, transcript anchors, and a concrete output, not a generic best-practice claim.
06
Recovery
Use "Recovery" to carry the idea forward: save the prompt, checklist, diagram, or operating rule that would make the next agent run better.
07
Post-run review
Connect "Post-run review" to How to Reverse Engineer Anything Better Than 99% of People by naming the claim, the evidence, and the artifact it should produce.
Example
Source-backed artifact packet
Convert the video into a scoped artifact request that includes the transcript claim, mechanism, acceptance criteria, and proof. The output should be a hermes-style agent-ops runbook with health checks, state transitions, logs, recovery steps, and review criteria..
Example
Hermes operations proof brief
Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the hermes operations pattern.
Example
Teach-back module
Transform the lesson into a definition, a Project state -> Session -> Queue/Kanban -> Tools -> Logs -> Recovery -> Post-run review diagram, one misconception, one practice exercise, and a check-for-understanding question.
Do not learn it wrong
Treating the title as the lesson without checking what the transcript actually says.
treating UI features as reliability
missing logs
no stop/recover path
Letting the lesson drift into feature cheerleading.
Letting the lesson drift into ops advice without logs/state.
Letting the lesson drift into assuming reliability from a demo alone.
Do not count this as learned until these are true.
01
State the transcript-backed claim in your own words: This video explains how Reverse Engineer Anything (REA) lets Claude use tools such as Ghidra, Hopper, or IDA through MCP to investigate compiled applications and rebuild selected behavior. It teaches learners to distinguish inspectable local logic from inaccessible cloud services, test recreations against observed behavior, and begin with one useful feature rather than cloning an entire product.
02
Explain the practical stakes without hype: New playlist item from Samin Yasar; queued for transcript-backed review, topic mapping, and a practical learning artifact.
03
Map the idea onto the Intent -> Task packet -> Context -> Agent run -> Evidence -> Review -> Reusable standard sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A task packet and review rubric that a coding agent could execute without wandering.
Put it into practice
Give this grounded prompt to Codex or Claude after watching.
You are helping me turn one specific YouTube video into real, durable learning.
Source video:
- Title: How to Reverse Engineer Anything Better Than 99% of People
- URL: https://www.youtube.com/watch?v=1LWPkLG6bP0
- Topic: Agentic Engineering
- My current learning frame: Select learner-owned, open-source, or explicitly authorized software, verify its license or terms permit inspection and modification, diagram one local feature's inputs and outputs, build a small recreation, and confirm redistribution rights before sharing it.
- Why this matters: New playlist item from Samin Yasar; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:00 / Evidence 1: "This new open source repo called reverse engineer anything lets you reverse engineer applications and build your own versions that you can customize and even resell. So, for example, this is an Mac app that I probably would..."
- 2:45 / Evidence 2: "share their own versions with a few conditions. That's the idea behind open-source software. You can read the code, and its license tells you the conditions for using it, changing it, and sharing it. So, when you build..."
- 6:58 / Evidence 3: "talking from there. And it essentially act as my personal service. And if I'm using cloud code, code X, whatever, or Hermes, I can do it all from one place if I'm out and about, right? So, for..."
- 10:31 / Evidence 4: "will also keep their logic and data on the device itself. For example, the Vitals app, because it's just something that's running on my computer all the time. And that's why REA was able to reverse engineer that..."
- 12:36 / Evidence 5: "right? Then I'm going to be showing with you with Claude. What you need to be doing is you can't do this in chat, okay? Very important. You need to be using something like Claude Code right here..."
- 16:31 / Evidence 6: "just put up with, but because of these open-source repos, now it's something you can understand, adapt, and actually build on for yourself or even for others. But, you know, if you have a mission, you can push..."
- 19:04 / Evidence 7: "source projects first. Use REA if you need to understand how everything works, but you can always have cloud code build a small version of it, you can test it, and then show it to one person who..."
Video-aware target:
- Prompt lane: Hermes operations
- Mechanism to extract: Identify the operations control that makes long-running agent work visible, recoverable, or safer.
- Artifact to produce: A Hermes-style agent-ops runbook with health checks, state transitions, logs, recovery steps, and review criteria.
- Artifact must include: health check; state model; permission boundary; log source; recovery action
Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, transcript support, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable mechanism from the video: Identify the operations control that makes long-running agent work visible, recoverable, or safer. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A Hermes-style agent-ops runbook with health checks, state transitions, logs, recovery steps, and review criteria.
5. Include:
- a plain-English definition of the core idea
- a diagram or structured model using this sequence: Project state -> Session -> Queue/Kanban -> Tools -> Logs -> Recovery -> Post-run review
- answers to these source questions: What operational failure is prevented? | What state is visible? | What can be recovered or redirected?
- 3 concrete examples that apply the video idea to real agentic work, such as Hermes Kanban triage; local model endpoint check; agent swarm recovery review
- 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: treating UI features as reliability; missing logs; no stop/recover path
- a checklist for the next real workflow, focused on: status, model/backend, tools, logs, recovery
- one practical exercise with a clear done signal: Write a runbook for restarting one stuck Hermes-style agent session.
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.
Quality bar:
- Make this specific to "How to Reverse Engineer Anything Better Than 99% of People", not a generic Agentic Engineering essay.
- Ground each ops recommendation in transcript evidence about state, queues, models, tools, security, logs, or recovery.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- Avoid these generic drifts: feature cheerleading; ops advice without logs/state; assuming reliability from a demo alone.
- If evidence is weak or missing, stop and say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.
Misconceptions
What to stop believing.
Agentic engineering means letting agents do everything.
It means designing work so agents can do bounded pieces well.
Separate what the video actually says from what you already believe about the topic.
3 source-backed takeaways with timestamps, confidence, and a transfer note.02
One useful artifact
Apply the video to a real workflow and produce a hermes-style agent-ops runbook with health checks, state transitions, logs, recovery steps, and review criteria..
A reusable artifact with a done signal and one verification step.03
Hermes operations teach-back card
Explain the hermes operations mechanism to someone who has not watched the video yet.
A 90-second explanation, one diagram, one example, and one misconception to avoid.
Recall check
Answer first, then reveal — without rewatching.
What new role does REA play compared with traditional reverse-engineering tools?
Why can tracing a cloud app's generate button not reveal the service that creates its videos?
Why was the Vitals app presented as a suitable reverse-engineering target?
Source shelf
Use the video as a doorway, then verify with primary sources.