How I Get Fable 5 Level Results with Any Model (Seriously) Using AI Harness Engineering
Argues that Fable 5's brilliance came less from the model than from Claude Code as its harness, and teaches what an agentic harness (or 'rig') is, the read-pick-run-check-done agent loop, and how to build one by stealing a template so any model, including open-source, can do long-horizon autonomous work.
Jordan Urbs35 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 Jordan Urbs; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to build and own a multi-agent agentic harness so you can plug any rented model into it and get long-horizon autonomous results, staying sovereign against model rug-pulls.
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.
6,826 cleaned transcript words reviewed across 1,936 timed caption segments.
Thesis
How I Get Fable 5 Level Results with Any Model (Seriously) Using AI Harness Engineering teaches a practical coding-agent workflow move: Argues that Fable 5's brilliance came less from the model than from Claude Code as its harness, and teaches what an agentic harness (or 'rig') is, the read-pick-run-check-done agent loop, and how to build one by stealing a template so any model, including open-source, can do long-horizon autonomous work.
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
Model plus harness
“We all know Fable 5 was one heck of a model. Then it got pulled. But if you know how to build a system that makes any LLM perform at that level, then you'll never have to worry...”
An AI agent is a model (the brain) plus a harness (the body: context, tools/MCPs, verification, done-checks, and memory); Fable 5 was so good because Claude Code was the harness built to maximize it, so Opus or open-source models in a good harness can do the same long-horizon work, and while you rent the intelligence you can own the rig. Draw the agent loop (read prompt, pick tool, run, check, done?) and label which parts of a harness you'd own versus which model you'd rent for a project you care about.
16:56
Sub-agents save context
“folder in open code using an open source model here via Venice, and I can run the same workflow, and it will do pretty much the same job, just with a different intelligence model behind it. So, if...”
In his content-repurposing harness the main orchestrator only loads what it needs and spawns sub-agents with fresh context windows (a content ideator that reads the thesis/positioning/glossary files, a voice reviewer that loads the voice-standard and stop-slop skills), because loading every document into one agent would burn hundreds of thousands of tokens and degrade quality against the million-token limit. Take a multi-step workflow you run and split it into specialized sub-agents, listing for each one only the specific files or skills it must read so the orchestrator stays lean.
23:06
Steal a template
“by hand is exactly the type of repeatable workflow that should be a harness. There you go. So, we're now building a harness inside Claude Code for this repetitive task for this particular project, which is a directory,...”
Don't build from scratch: copy a proven harness like Scott Graham's Safe Agentic Workflow (a scaled-agile 11-agent team) URL, paste it into your IDE or the Open Code desktop app, describe what you want, and shift into plan mode; he even builds harnesses conversationally with no URL, and the guiding rule is build with frontier models then execute with cheaper open-source ones (he uses the Venice API to switch per task). Grab the Safe Agentic Workflow template URL, open a new session, and prompt your AI to plan a harness for one repetitive task in your work, then have it scaffold the agents and commands.
01
Inspect context
Start with this video's job: Argues that Fable 5's brilliance came less from the model than from Claude Code as its harness, and teaches what an agentic harness (or 'rig') is, the read-pick-run-check-done agent loop, and how to build one by stealing a template so any model, including open-source, can do long-horizon autonomous work. Treat "Inspect context" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:00, where the video says: “We all know Fable 5 was one heck of a model. Then it got pulled. But if you know how to build a system that makes any LLM perform at that level, then you'll never have to worry...”
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 16:56, where the video says: “folder in open code using an open source model here via Venice, and I can run the same workflow, and it will do pretty much the same job, just with a different intelligence model behind it. So, if...”
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: Argues that Fable 5's brilliance came less from the model than from Claude Code as its harness, and teaches what an agentic harness (or 'rig') is, the read-pick-run-check-done agent loop, and how to build one by stealing a template so any model, including open-source, can do long-horizon autonomous work.
02
Explain the practical stakes without hype: New playlist item from Jordan Urbs; 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: How I Get Fable 5 Level Results with Any Model (Seriously) Using AI Harness Engineering
- URL: https://www.youtube.com/watch?v=R_Nf-IDVZEg
- Topic: Creative Automation
- My current learning frame: Clone a proven harness template into your IDE or Open Code, prompt a frontier model to adapt it into a rig for one repeatable task, then run that rig with a cheaper open-source model to prove you own the body while renting the brain.
- Why this matters: New playlist item from Jordan Urbs; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:00 / Evidence 1: "We all know Fable 5 was one heck of a model. Then it got pulled. But if you know how to build a system that makes any LLM perform at that level, then you'll never have to worry..."
- 3:05 / Evidence 2: "essence, an AI agent is really a model plus a harness. And then, this is really important to remember, in my opinion, because Fable was the model. Okay? The reason Fable was so freaking good because the Claude..."
- 6:57 / Evidence 3: "am I going to need which model, for either saving money or making sure I get the best performance possible for that specific task. So, what this means in essence is AI writes the code now, makes the..."
- 12:08 / Evidence 4: "and so we have another dot cloud folder, which says agents repurpose threads. So this agent produces X content from a transcript analysis. And here we are in there. So in my main folder, it's got my agent..."
- 16:56 / Evidence 5: "folder in open code using an open source model here via Venice, and I can run the same workflow, and it will do pretty much the same job, just with a different intelligence model behind it. So, if..."
- 23:06 / Evidence 6: "by hand is exactly the type of repeatable workflow that should be a harness. There you go. So, we're now building a harness inside Claude Code for this repetitive task for this particular project, which is a directory,..."
- 34:26 / Evidence 7: "build. Start by stealing a good one. You're obviously not really stealing. Shout out to Scott Graham, thank you for providing this to the world. It's awesome. Safe agentic workflow, the link is below. You can also just..."
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 "How I Get Fable 5 Level Results with Any Model (Seriously) Using AI Harness Engineering", 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.
According to the video, why was Fable 5 so impressive, and what does that imply for using other models?
Why does the main orchestrator spawn sub-agents instead of loading everything itself?
What is the recommended way to start building a harness, and the build-versus-execute rule?
Source shelf
Use the video as a doorway, then verify with primary sources.
