The argument in one line.
Across three identical one-shot build tests, GPT-5.6's Soul agent consistently out-designed and out-executed Fable 5, despite costing roughly eight times more and taking hours longer to finish.
Read if. Skip if.
- You use agentic coding tools (Claude Code, Codex, Fable) for real one-shot builds and want evidence on which model actually ships better UI, not just benchmark scores.
- You're weighing whether a slower, pricier agent run is worth it for design quality on a build you can't babysit.
- You build clone-style products — mockup tools, drop sites, data-driven platforms — and want to see what one unsupervised agent pass can and can't pull off.
- You're looking for exact prompts and step-by-step setup rather than a side-by-side outcome comparison.
- You don't use agentic coding tools and have no stake in a Claude-vs-GPT model comparison.
The full version, fast.
A creator ran the exact same prompts through Fable 5 and GPT-5.6 (via OpenAI's Codex/Soul agent) across three one-shot builds: a pixel-for-pixel clone of the mockup tool shots.so, an invented MSCHF-style viral product drop, and a from-scratch interactive NYC history platform. In every test, the slower and far more expensive Soul agent produced more thorough, more interactive, better-designed output — extracting working animation controls Fable skipped, building a multi-step interactive drop instead of a static page, and pulling in more real data on the learning platform. Fable only caught up after a second round of explicit feedback. The trade-off: Soul took roughly 6-9x longer and cost up to 8x more per build, and both agents' built-in cost trackers under-reported actual usage.
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.

01 · Intro
Cold open framing the test: GPT-5.6 versus Fable 5 on three identical one-shot prompts, no revisions, deployed live.

02 · Build 1: Cloning shots.so pixel-for-pixel
Both agents run the clone-app-pat-pro pipeline against the mockup tool shots.so. Fable finishes in 30 minutes; GPT-5.6 Soul takes nearly three hours but extracts far more of the real UI, including working layout presets and an animation timeline.

03 · Build 2: The MSCHF test — invent a viral drop
Each agent invents an original MSCHF-style product drop and builds its site. Soul ships a confusing but highly interactive 'Human Resources' captcha-factory concept; Fable ships a clearer but static 'free shirt paid in fees' page.

04 · Build 3: An NYC learning platform from a rough idea
Given only a loose one-paragraph idea, both agents build a click-through NYC history site pulling from Wikipedia. Both underdeliver on the requested interactivity; after one round of feedback, both rebuild it as an explorable 3D city.

05 · The cost breakdown
Per-build time and cost for each agent across all three tests, plus a caveat that built-in usage trackers in Claude Code and Codex undercount real session cost.

06 · Final thoughts
Verdict: GPT-5.6 Soul was more thorough, followed directions better, and designed better across all three tests — despite costing and taking substantially more to run.
Lines worth screenshotting.
- GPT-5.6's Soul agent took nearly three hours and cost about $93 to clone shots.so, while Fable 5 finished the same clone in 30 minutes for $12.67 — yet Soul's clone was judged the clear winner on completeness.
- The MSCHF-style drop test cost $20.40 on Fable 5 (15 minutes) versus a reported $5.05 on GPT-5.6 Soul (30 minutes) — the cheapest build of the three came from the same agent that was most expensive on the other two.
- The NYC learning platform run cost $95 on Fable 5 versus $11 on GPT-5.6 — agent cost per task swings wildly and doesn't track consistently with either the agent or the build type.
- A single-page product idea with a clear premise (a 'free t-shirt' funded entirely by itemized fees) read as less creative than a more disorienting, multi-step concept (a captcha-factory 'prove you're human' shift) even though the disorienting one was harder to fully understand.
- Both agents defaulted to a conventional click-through, page-based interface for an 'interactive learning platform' brief until given explicit follow-up feedback demanding a 3D, immersive environment — the first unprompted attempt undersold what both models could build.
- One round of concrete revision feedback turned two flat, page-based NYC prototypes into two real 3D explorable city maps within about 30 minutes each — the gap was in the initial interpretation of 'interactive,' not agent capability.
- Built-in cost/usage commands in both Claude Code and the ChatGPT/Codex app under-reported real session cost compared to a third-party CLI cost tool (npx ccusage) run against the same session logs.
- A named, reusable cloning pipeline (recon, extraction, design spec, architecture, build, QA, fix loop, polish, deploy) run step-by-step produced a more feature-complete pixel clone than an agent that finished in a fraction of the time.
- Both agents deployed live, working builds to the internet from a single prompt with zero revisions across all three tests — the differentiator wasn't functionality, it was design depth and thoroughness.
- Soul was slower on every single build in this test, running against the common finding that GPT-class agents are typically faster than Claude-class agents — the creator flagged this as a possible anomaly, not a settled pattern.
The pricier, slower AI agent built better software three times running.
Across a pixel-perfect clone, an invented product drop, and a from-scratch platform, the agent that took the longest and cost the most consistently shipped more interactive, more complete builds — and one round of concrete feedback closed the interactivity gap faster than a better initial prompt would have.
- A pixel-for-pixel clone test still measures real skill: matching padding, corner radius, animation timelines, and export behavior is much harder than copying static layout.
- The agent that took three hours and cost roughly 8x more extracted working interactive controls — layout presets, an animation timeline, adjustable light — that the faster, cheaper agent skipped entirely.
- Following a written cloning pipeline (recon, extraction, design spec, architecture, build, QA, fix loop, polish, deploy) step by step produced a more feature-complete result than an agent that finished fast without visibly working each stage.
- Asking a model to invent a viral concept, not just execute a spec, is a much harder creativity test than cloning — the two agents produced very different levels of interactive polish, a full multi-step simulation versus a single static page.
- A confusing but committed concept read as more successful than a clearer, safer one, because it took more creative risk and built more interaction, even though it was harder to fully understand.
- Telling an agent not to build 'just a static page' only worked for one of the two models — the instruction alone didn't guarantee a multi-step, interactive execution.
- With almost no creative direction, both agents defaulted to a conventional page-by-page browsing experience instead of the interactive, immersive environment that was explicitly requested.
- A single round of concrete feedback was enough to get both agents to rebuild the same rough idea as a real 3D explorable city map — the gap was in the first unprompted attempt, not in agent capability.
- Design quality and information completeness didn't come from the same agent in either version — one produced better visuals with less pulled-in content, the other more comprehensive data with a less appealing interface.
- The costlier, slower run didn't correlate with a worse result — it was the version judged better across all three tests.
- Subscription-plan agent tools don't reliably surface accurate per-session cost — built-in /cost and /usage commands understated real usage compared to a separate CLI cost-tracking tool run against the same session.
- If you're tracking real spend on agentic coding work, pull-based API billing gives a cleaner number than a flat subscription plan, where per-task cost is currently hard to audit.
Terms worth knowing.
- One-shot build
- A single prompt sent to an AI coding agent with no follow-up revisions, used as the controlled test condition before a second 'two-shot' round with feedback.
- Clone-app-pat-pro pipeline
- A named, reusable process for cloning an existing app or site step by step: recon, extraction, design spec, architecture, build, QA, a fix loop, polish, then deploy.
- MSCHF drop
- A limited, deliberately outlandish product release style pioneered by the collective MSCHF, known for stunts like selling individually numbered pieces of a cut-up sculpture.
- Wikimedia Commons API
- A public interface for pulling text and media directly from Wikipedia/Wikimedia's underlying data, used here as the fact source for the AI-built NYC learning platform.
Things they pointed at.
Lines you could clip.
“Same rules for both, a single one shot output, no revisions, deployed live to the Internet.”
“The final runtime, by way, for GPT five six, two hours and fifty one minutes.”
“Soul just absolutely crushed it.”
“Four five six, as mentioned, it took three hours and costs almost a $100 in usage costs.”
“I can't believe I'm saying this, but I really think Soul took the cake here.”
Word for word.
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
The bait, then the rug-pull.
OpenAI's GPT-5.6 finally had an answer to Fable 5's month-long run at the frontier — so the only way to settle it was to give both agents the exact same prompt, three times, and watch what they actually shipped.
Named ideas worth stealing.
The clone-app-pat-pro pipeline
- Recon
- Extraction
- Design spec
- Architecture
- Build
- QA
- Fix loop
- Polish
- Deploy
A step-by-step process for cloning an existing app: capture the live product via screenshots/interaction, extract assets and structure, write a design spec, architect the build, implement, then run QA and polish loops before deploying.
How they asked for the click.
“if you wanna see how GPT five six stacks up against other models with a real breakdown of benchmarks... you can check out this video here. And send me your build ideas too.”
soft, low-pressure — points to a benchmark video and invites viewer-submitted build ideas for future tests, no hard sell










































































