I Replaced Opus 4.7 With a Free Chinese AI (INSANE)
This video demonstrates running the free MiMo (Xiaomi) V2.5 Pro model inside Claude Code via OpenRouter, combined with the creator's Astro Builder skill and the Superpowers plugin, to generate a full Astro business website with images, a Turso database, lead-gen forms, and an admin login.
Income stream surfersWatchTranscript found
Quick learning frame
Read this before watching.
Coding-agent workflow is the loop of inspect, route, plan, edit, verify, summarize, and decide what should be automated next.
New playlist item from Income stream surfers; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: Configuring Claude Code to run a free, non-Anthropic LLM through OpenRouter and pairing it with reusable skills (Astro Builder + Superpowers) to produce a complete database-backed website at near-zero model cost.
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.
01Inspect context
02Route tool
03Plan work
04Edit safely
05Verify behavior
06Report next step
Deep lesson
Turn this video into working knowledge.
1,285 cleaned transcript words reviewed across 383 timed caption segments.
Thesis
I Replaced Opus 4.7 With a Free Chinese AI (INSANE) teaches a practical coding-agent workflow move: This video demonstrates running the free MiMo (Xiaomi) V2.5 Pro model inside Claude Code via OpenRouter, combined with the creator's Astro Builder skill and the Superpowers plugin, to generate a full Astro business website with images, a Turso database, lead-gen forms, and an admin login.
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:14
Stack overview
“going to be testing out Mimo inside Claude code, but with a couple of differences. So, this is Mimo Claude code inside, sorry, uh using Astro builder skill, right? This is a completely free skill that you can...”
The build combines three swappable pieces: a model (MiMo V2.5 Pro), a domain skill (Astro Builder, which scaffolds an Astro site with database, lead gen, and admin), and a workflow plugin (Superpowers) — showing that the model is just one interchangeable layer in the pipeline. List the three components used here and identify which layer each one controls (reasoning, scaffolding, workflow) so you can swap any single layer later.
3:05
Point Claude Code at MiMo
“used for free today inside Claude code, right? So, for example, Owl Alpha most likely is a pretty good model, right? Nematic 3 Nano, a lot of people talk about this model as being decent. Deep Seek V4...”
You set Claude Code's model to Xiaomi/MiMo and verify it is actually running by checking the OpenRouter logs for a matching timestamped request, rather than trusting the config alone; running out of credits mid-build just requires topping up tokens on OpenRouter. Set Claude Code to a non-Anthropic OpenRouter model, then open OpenRouter logs and confirm your request appears with the right model name and timestamp.
5:11
Free models trick
“Um should already be logged in. Let's see here. There we go. Bang. Look at that. So, a complete build with a Chinese AI is now possible, which I didn't think I'd be saying for a long time.”
On OpenRouter you can sort the model list by prompt pricing down to free (e.g. Owl Alpha, Nemotron Nano, DeepSeek V4 Flash Free, Gemma 431B) and route any of them into Claude Code, making Claude Code usable at zero model cost. Open OpenRouter, filter prompt pricing to free, and pick one free coding model to wire into Claude Code as your no-cost setup.
01
Inspect context
Start with this video's job: This video demonstrates running the free MiMo (Xiaomi) V2.5 Pro model inside Claude Code via OpenRouter, combined with the creator's Astro Builder skill and the Superpowers plugin, to generate a full Astro business website with images, a Turso database, lead-gen forms, and an admin login. Treat "Inspect context" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:14, where the video says: “going to be testing out Mimo inside Claude code, but with a couple of differences. So, this is Mimo Claude code inside, sorry, uh using Astro builder skill, right? This is a completely free skill that you can...”
02
Route tool
Use "Route tool" to locate the part of the coding-agent workflow mechanism the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 3:05, where the video says: “used for free today inside Claude code, right? So, for example, Owl Alpha most likely is a pretty good model, right? Nematic 3 Nano, a lot of people talk about this model as being decent. Deep Seek V4...”
03
Plan work
Turn "Plan work" into the reusable artifact for this lesson: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal. This is where watching becomes something you can inspect and reuse.
04
Edit safely
Use "Edit safely" 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
Verify behavior
Use "Verify behavior" 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
Report next step
Use "Report next step" to carry the idea forward: save the prompt, checklist, diagram, or operating rule that would make the next agent run better.
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 coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal..
Example
Coding-agent workflow proof brief
Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the coding-agent workflow pattern.
Example
Teach-back module
Transform the lesson into a definition, a Inspect context -> Route tool -> Plan work -> Edit safely -> Verify behavior -> Report next step 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.
choosing tools by hype
losing context across agents
letting parallel sessions become invisible
Letting the lesson drift into generic Codex vs Claude comparison.
Letting the lesson drift into feature lists without task routing.
Letting the lesson drift into claims that ignore limits or recovery.
Do not count this as learned until these are true.
01
State the transcript-backed claim in your own words: This video demonstrates running the free MiMo (Xiaomi) V2.5 Pro model inside Claude Code via OpenRouter, combined with the creator's Astro Builder skill and the Superpowers plugin, to generate a full Astro business website with images, a Turso database, lead-gen forms, and an admin login.
02
Explain the practical stakes without hype: New playlist item from Income stream surfers; queued for transcript-backed review, topic mapping, and a practical learning artifact.
03
Map the idea onto the Inspect context -> Route tool -> Plan work -> Edit safely -> Verify behavior -> Report next step sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
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: I Replaced Opus 4.7 With a Free Chinese AI (INSANE)
- URL: https://www.youtube.com/watch?v=9MPYITkwAKw
- Topic: Agent Architecture
- My current learning frame: Wire a free OpenRouter model into Claude Code, add the Astro Builder skill, and generate a small business site — then fix the one realistic failure shown here (a disconnected Turso database breaking the contact form) by re-authenticating the CLI.
- Why this matters: New playlist item from Income stream surfers; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:14 / Evidence 1: "going to be testing out Mimo inside Claude code, but with a couple of differences. So, this is Mimo Claude code inside, sorry, uh using Astro builder skill, right? This is a completely free skill that you can..."
- 3:05 / Evidence 2: "used for free today inside Claude code, right? So, for example, Owl Alpha most likely is a pretty good model, right? Nematic 3 Nano, a lot of people talk about this model as being decent. Deep Seek V4..."
- 5:11 / Evidence 3: "Um should already be logged in. Let's see here. There we go. Bang. Look at that. So, a complete build with a Chinese AI is now possible, which I didn't think I'd be saying for a long time."
Video-aware target:
- Prompt lane: Coding-agent workflow
- Mechanism to extract: Find the workflow rule that explains when and how to use Codex, Claude Code, browser control, dashboards, or manual review.
- Artifact to produce: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
- Artifact must include: task class; agent/tool choice; context packet; verification step; handoff/recovery rule
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: Find the workflow rule that explains when and how to use Codex, Claude Code, browser control, dashboards, or manual review. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
5. Include:
- a plain-English definition of the core idea
- a diagram or structured model using this sequence: Inspect context -> Route tool -> Plan work -> Edit safely -> Verify behavior -> Report next step
- answers to these source questions: What workflow pain is being solved? | What exact coordination mechanism is shown? | What evidence proves it changes the work?
- 3 concrete examples that apply the video idea to real agentic work, such as rate-limit routing; browser verification after a UI edit; long-running /goal session review
- 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: choosing tools by hype; losing context across agents; letting parallel sessions become invisible
- a checklist for the next real workflow, focused on: routing decision, context portability, verification, handoff summary
- one practical exercise with a clear done signal: Route three recent tasks across Codex, Claude, browser checks, and manual review with a reason for each.
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 "I Replaced Opus 4.7 With a Free Chinese AI (INSANE)", not a generic Agent Architecture essay.
- Each workflow rule must point to a timestamped claim or demo moment, then state what remains unproven.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- Avoid these generic drifts: generic Codex vs Claude comparison; feature lists without task routing; claims that ignore limits or recovery.
- 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.
A better model automatically makes a better agent.
The model matters, but harness design determines whether the system can act safely and repeatably.
More tools always help.
Every tool increases surface area. Strong agents have the right tools with clear permissions.
Memory means saving everything.
Useful memory is compressed, curated, and tied to future decisions.
Practice studio
Learning only counts when you make something.
01
Transcript evidence map
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 coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal..
A reusable artifact with a done signal and one verification step.03
Coding-agent workflow teach-back card
Explain the coding-agent workflow 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.
After setting Claude Code to use MiMo via OpenRouter, what specific step does the presenter take to confirm the model is actually serving requests rather than trusting the config?
What exact trick on OpenRouter does the video give for running Claude Code at zero model cost, and which models does it name as usable that way?
Beyond the MiMo model itself, what two additional swappable components make up the build, and what does each contribute?
Source shelf
Use the video as a doorway, then verify with primary sources.
