Skip to content
Agents tracked: 502 Releases (7d): 613 Agent status: 4 with issuesSince last limit reset: Claude 7d · Codex 5d For AI agents: Markdown Updated Nov 18, 2026

✓ Checked

Opus 5.5 Motion Design: What 'One-Prompt' Videos Really Take

An X Article says viral Opus 5.5 videos hide long briefs, high effort and a critique loop. We checked its technical claims against Claude Code's docs, HyperFrames and the two repos it recommends: mostly right, with three overstatements.

On October 2, 2026, @seeconvm published an X Article titled "Opus 5.5 Motion Design: What the Viral 'One-Prompt' Videos Are Hiding". Its argument is that the launch films and music videos people posted after Claude Opus 5.5 came out were rarely one prompt. The good ones, it says, started from long briefs, a skills folder and runs that went on for hours, and all of them had a step where the model looked at its own frames and fixed them.

Most of the article is a method in eight steps, illustrated with other creators' posts. We cannot check view counts or what other people typed into their sessions, so this check covers the technical claims: how a code-made video is rendered, what effort levels do in Claude Code, what Opus can look at, and the two GitHub repositories the article tells you to clone. We read Anthropic's announcement and docs, the HyperFrames README, both repositories and GitHub's API on November 6, 2026.

How a code-made video is rendered

The article's first step is the right place to start. The model never writes a video file: it writes a program that can draw any moment of the film, and other tools turn that program into pictures. The repositories behind the viral clips say the same. PDoomVideo's renderer paints frames in headless Chrome and encodes the MP4 with ffmpeg, ClaudeAnimationBase needs Node.js, Google Chrome and ffmpeg, and HyperFrames packages the idea as a framework whose README says the renderer seeks each frame in headless Chrome and encodes the result with FFmpeg, "so the same input produces the same video".

Brief, assets and skills in files→Opus writes a page that draws frame t→Headless Chrome seeks every frame→ffmpeg encodes the MP4→Contact sheet goes back to Opus
The pipeline described by the article, the HyperFrames README and the PDoomVideo and ClaudeAnimationBase repositories. The dashed step is the critique loop the article treats as the one every viral clip had.

That is why the article calls seekability the rule you cannot bend. Its example clip of 15 seconds at 60 fps is 900 frames, and each must render from its time alone, in any order and on any render worker. A spring or a timer that depends on the previous frame breaks that, which is the point of its section on closed-form springs.

The claims, checked

The article says What the sources say Verdict
Opus 5.5 came out on September 22 Anthropic's announcement is dated September 22, 2026 Right
Opus 5.5 starts on medium effort Claude Code's docs list medium as the default on Opus 5.5, Sonnet 5.5 and Haiku 5.5 Right
Medium is for small fixes The docs pitch medium at day-to-day work with a clear scope, such as building a new feature; small edits like a rename are what low is for Understated
Every viral one-shot ran on xhigh or max ClaudeAnimationBase's test videos ran on xhigh, but PDoomVideo's README says its first generation ran on Opus 5.5 at Medium Overstated
Use max when the launch depends on it The docs warn that max may show diminishing returns and is prone to overthinking Test first
"go all out" stacks extra effort on top of xhigh Claude Code recognizes one keyword, ultrathink; other phrases pass through as ordinary prompt text Not a switch
Opus reads images, so it can check its own frames Anthropic's vision docs price image input on Opus 5.5; ClaudeAnimationBase's agent renders contact sheets to check its work Right
A CLAUDE.md is read on every run Claude Code's memory docs: Claude reads CLAUDE.md files at the start of every session Right
The PDoom repo has 1.1K stars 2,847 on November 6, 2026, per GitHub's API Out of date

Effort in Claude Code, without the folklore

The article is right that the default changed. Claude Code's model docs say Opus 5.5 defaults to medium, one level below Opus 5's default of high, and, as reported by Anthropic, Opus 5.5 at medium matches or exceeds Opus 5 at high on coding and knowledge-work evaluations. Whether a film needs more is a separate question, and the two repos the article recommends disagree with its "every viral one-shot" line: ClaudeAnimationBase's author made all test videos on xhigh and writes that the reasoning level tracks how extravagant and detailed the scenes get, while the first PDoomVideo generation ran on medium.

lowQuick exchanges you review one by one: a first sketch, a rename
medium (default)Scoped day-to-day work on Opus 5.5
highWork where checking matters and edge cases are likely
xhighDeeper reasoning at a higher token spend
maxHard problems left to Claude; may overthink, test before using it widely
Claude Code's effort levels, summarized from its model configuration docs. Each step up spends more tokens per turn.

How to set them, from the same docs:

  • /effort xhigh sets the level for the session; /effort alone opens a slider.
  • claude --effort xhigh starts one session at that level, and the CLAUDE_CODE_EFFORT_LEVEL environment variable outranks a level picked in the session.
  • The effortLevel setting accepts low to xhigh as a saved default. The docs say max is not accepted there, so max stays a per-session choice.
  • ultrathink anywhere in a prompt asks for deeper reasoning on that one turn without changing the session level. Typed in the terminal, it can raise the turn to xhigh; it needs Claude Code v2.1.311 or later. Phrases like "think hard" are not keywords, and neither is "go all out".
  • A skill or subagent file can set its own effort in its frontmatter. That matters for the article's last step: if you pack your video pipeline into a skill, the level travels with it.

The critique loop is cheap if you send a contact sheet

The article's "critic" step asks ffmpeg to tile frames into a contact sheet and hands that one image to Opus. The arithmetic backs it up. Anthropic's vision docs put a 1000×1000 image on Opus 5.5 at about $5.18 per thousand images. By our calculation, sending every frame of the 900-frame example at that size would cost about $4.66 per review pass, against about $0.005 for one contact sheet.

All 900 frames, one pass$4.66 One contact sheet$0.005
Image input cost only, by our calculation from the per-image price in Anthropic's vision docs, assuming each image is 1000×1000. Text tokens come on top.

Text tokens are where long runs add up. Anthropic lists Opus 5.5 at $4 per million input tokens and $20 per million output tokens, with cache reads at $0.20 per million, and says it costs 40% less to run than Opus 5 (as reported). On a Claude subscription the same run draws on the plan's usage limits instead; Anthropic says it raised the five-hour limits on Pro, Max, Team and seat-based Enterprise plans with this release.

The two repos to clone

PDoomVideo is the source of a music video for "I'm Upping My P(doom)". Its README matches the article's description: the video has nine chapters, one file each, and Opus wrote ANIMATION_GUIDE.md to brief the subagents it ran in parallel. It also says everything in the repository was generated by the model. Two things the article leaves out: GitHub's API shows no license for the repository, so the code stays under its author's copyright and is for reading, not reuse; and the song is not the author's, as the README's credits explain.

ClaudeAnimationBase is the starter kit built from it, for hand-painted character animation in p5.js. Its README shows the loop the article teaches: the model storyboards first, builds shot by shot and renders contact sheets to check its own work. It also warns that without a dedicated GPU the watercolour fills render in seconds per frame. Our earlier check of Opus 5.5 video repos covers its license and six more repos.

What the article gets right, and what it leaves out

It gets the important parts right: the video is a program, any frame must render on its own, real product screens beat invented ones, and a model that can look at its frames should be made to. Keeping the decisions in files rather than in one chat is also how Claude Code is meant to work: CLAUDE.md for house rules, a skill for the pipeline.

What it leaves out:

  • Licenses. A studio that renders for clients has to pick its framework with care. Remotion is free for individuals and companies of up to 3 employees and paid above that; HyperFrames is Apache 2.0; FFmpeg is LGPL 2.1 or later by default. The article's "zero-dependency route" avoids the question only because Opus writes its own renderer.
  • Render time. A seekable film is deterministic, not fast. ClaudeAnimationBase's GPU warning is the only render-time figure in the sources the article points to.
  • The anecdotes. View counts, the 12-hour overnight run, the 9,500-character brief and the $1,200 agency price for a launch film come from other people's posts. We could not check them, and the article does not link most of them.
  • The effort rules. "Every viral one-shot ran on xhigh or max" is contradicted by one of the two repos it recommends, and "go all out" does nothing that any other sentence would not.

AgentGid data

Claude Code, the agent the article builds on, is #1 of all tracked agents by Gid Score (84.6 on November 5, 2026), with 12,690,433 weekly package downloads. It is included in the Pro plan ($17 a month billed annually or $20 monthly), Max ($100) and Ultra ($200); the Free plan does not include it. For the render side, AgentGid's video assembly catalog lists HyperFrames, Remotion, FFmpeg and Manim with their licenses side by side.

Where to start

  1. Pick the renderer first: the HyperFrames plugin for Claude Code if you want a framework, or a clone of ClaudeAnimationBase if you want hand-drawn character animation.
  2. Write the brief, the asset list and the house rules into files before the first render.
  3. Run new films at /effort xhigh, use ultrathink for a single hard turn, and try max only on a test scene.
  4. After every render, send one contact sheet back with a list of what to fix, not the whole film.

The verdict

A useful article with the right core: code-made video is a seekable program plus a review loop, and the brief matters more than the prompt. Three of its details do not hold up against the docs and its own sources: medium effort is not just for small fixes, not every viral film ran on xhigh or max, and "go all out" is not an effort setting. The star count it gives for PDoomVideo is out of date, and the repo it tells you to clone has no license.

Everything above comes from Anthropic's announcement and docs, the HyperFrames, PDoomVideo and ClaudeAnimationBase repositories, GitHub's API and AgentGid's own data, read November 6, 2026. We did not render a video or run these tools ourselves.

Was this useful?

Agents mentioned in this guide

# Agent Gid Score Downloads 7d 7d 30d Stars Latest release
1
Claude CodeAnthropic
87 17.5M up 23.5% down 0.7% 156K+134/day 2.1.3262d ago

Live table, updated daily (figures as of Nov 18, 2026); numbers in the text above are as of the dates given there. "#" is the rank among products of the same kind by Gid Score, our 0-100 composite of adoption, community, attention and momentum (how it is calculated); a dash means no public data.