My NEW AI Editor Completely FREE 0$ (No Subscription)
This lesson demonstrates a zero-subscription video-editing workflow built from the OpenCode terminal agent, the free GLM 5.3 Flash model, and a reusable Editor V1 skill. It explains why explicit editing rules let a less capable model complete the work, which editing styles remain out of reach, and how to install, test, and iterate on the setup.
Jad M.H | AI Automation10 minTranscript 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 Jad M.H | AI Automation; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to assemble and operate a skill-guided, no-subscription AI video-editing workflow while matching the task's complexity to the model's limits.
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.
2,091 cleaned transcript words reviewed across 554 timed caption segments.
Thesis
My NEW AI Editor Completely FREE 0$ (No Subscription) teaches a practical coding-agent workflow move: This lesson demonstrates a zero-subscription video-editing workflow built from the OpenCode terminal agent, the free GLM 5.3 Flash model, and a reusable Editor V1 skill. It explains why explicit editing rules let a less capable model complete the work, which editing styles remain out of reach, and how to install, test, and iterate on the setup.
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:48
Remove The Cost Barrier
“put my card somewhere. I used a free open model called GLM 5.3 Flash. So what I did before doing this video, I went online trying to see if somebody has ever done it before. Sure, I have...”
The demonstrated edit used no cloud subscription, API key, account, or paid credits: the local computer handled cutting, transitions, graphics, rendering, and sound mixing while the large GLM 5.3 Flash model ran on OpenCode's servers. This makes experimentation accessible before a beginner knows whether AI editing will work for them. Choose a short raw clip and list every local operation and hosted-model operation the demonstrated workflow would use to edit it.
2:56
Skills Carry The Method
“It's like Cloud Code, an AI agent that lives in your terminal, but it's free and open source. And here's the part that you might miss. Open code reads the same skill folders as Claude Code. So my...”
The workflow depends on three pieces working together: OpenCode as the agent, GLM 5.3 Flash as the free model, and Editor V1 as the detailed recipe. The skill encodes pacing, colors, sound, caption placement, and forbidden choices, so the model can follow a tiny prompt instead of deriving the editing system itself. Write five concrete editing rules for a repeatable style, including one pacing rule, one caption rule, and one constraint the model must never break.
7:44
Install Test Iterate
“clot code inside it. Don't worry about it. Open code reads the same folder. It finds the zip, installs the skill and then installs all the free tools for you. FFmpeg, Python, the video render, and the speech...”
The setup selects the free GLM model at maximum reasoning, installs the skill and dependencies such as FFmpeg, Python, the renderer, and speech model, then verifies them with a seven-second test. Actual use begins in a fresh session with a short clip, followed by timestamped revision notes; the presenter warns that the code-heavy motion-graphics skill is beyond current open models. Run the setup's short test, then edit a sub-minute clip and give one revision note tied to an exact second rather than starting with a long video.
01
Inspect context
Start with this video's job: This lesson demonstrates a zero-subscription video-editing workflow built from the OpenCode terminal agent, the free GLM 5.3 Flash model, and a reusable Editor V1 skill. It explains why explicit editing rules let a less capable model complete the work, which editing styles remain out of reach, and how to install, test, and iterate on the setup. Treat "Inspect context" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:48, where the video says: “put my card somewhere. I used a free open model called GLM 5.3 Flash. So what I did before doing this video, I went online trying to see if somebody has ever done it before. Sure, I have...”
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 2:56, where the video says: “It's like Cloud Code, an AI agent that lives in your terminal, but it's free and open source. And here's the part that you might miss. Open code reads the same skill folders as Claude Code. So my...”
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 lesson demonstrates a zero-subscription video-editing workflow built from the OpenCode terminal agent, the free GLM 5.3 Flash model, and a reusable Editor V1 skill. It explains why explicit editing rules let a less capable model complete the work, which editing styles remain out of reach, and how to install, test, and iterate on the setup.
02
Explain the practical stakes without hype: New playlist item from Jad M.H | AI Automation; 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: My NEW AI Editor Completely FREE 0$ (No Subscription)
- URL: https://www.youtube.com/watch?v=S5Y3Hp2P740
- Topic: Creative Automation
- My current learning frame: Define a compact editing style as explicit rules, verify the free toolchain with a seven-second render, and use it to edit one short clip followed by timestamped feedback.
- Why this matters: New playlist item from Jad M.H | AI Automation; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:48 / Evidence 1: "put my card somewhere. I used a free open model called GLM 5.3 Flash. So what I did before doing this video, I went online trying to see if somebody has ever done it before. Sure, I have..."
- 2:56 / Evidence 2: "It's like Cloud Code, an AI agent that lives in your terminal, but it's free and open source. And here's the part that you might miss. Open code reads the same skill folders as Claude Code. So my..."
- 5:36 / Evidence 3: "doing is building the skill in open code. Claude is much more smarter. It's it's better to build the skill in Claude. And that's what I did. I built in Claude and then gave it to you so..."
- 7:44 / Evidence 4: "clot code inside it. Don't worry about it. Open code reads the same folder. It finds the zip, installs the skill and then installs all the free tools for you. FFmpeg, Python, the video render, and the speech..."
- 9:15 / Evidence 5: "better from here. So, if money was the thing that was a little bit blocking you, I think this is the best way to start content. The skill is free in my school community. Link is in description."
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 "My NEW AI Editor Completely FREE 0$ (No Subscription)", not a generic Creative Automation 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.
Creative AI removes the need for taste.
It increases the need for taste because output volume explodes.
The best prompt is enough.
References, critique, iteration, and post-production matter just as much.
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.
Which parts of the demonstrated workflow ran locally, and where did the model run?
Why can the workflow use a tiny editing prompt instead of a massive one?
What proves the installation is ready before editing a real video?
Source shelf
Use the video as a doorway, then verify with primary sources.
