A viral video format is a function you can call again

A video that hits ten million views is not lucky footage. It is a structure that was executed well: a hook inside the first two seconds, beats landing on a predictable rhythm, captions appearing one phrase at a time, a payoff that arrives before the viewer decides to leave. Structures are reproducible. That is the whole premise behind treating a viral format as something you can call again instead of something you hope to catch twice.

"Clone" gets misunderstood here, so let me draw the line first. Cloning copies structure — beat order, pacing, caption rhythm, how much time the setup gets before the turn. It does not copy someone's footage, voiceover or script. Reusing another creator's material is a copyright question, not a workflow feature. What you take is the shape, and you fill it with your own product, presenter and words.

Why a coding agent, and not a timeline

Editing tools put the structure inside a binary project file. You cannot diff it, you cannot ask for a variant, and you cannot re-apply the format to different content without doing the manual work again.

A coding agent flips that. The composition becomes text: a script file with segments and takes, a media manifest, a stylesheet. Text an agent can read, edit and re-run is text you can version — and that is the difference between "make one video" and "make a hundred variants of this video", which is what short-form content actually needs.

Hypit is the open-source tooling that does this — TypeScript, roughly ten thousand stars, MIT-ish public repo, install with one command:

npx skills add hypit-ai/hypit -g

The -g registers the skill globally so any project can use it. It works with Claude Code, Codex, Cursor, or anything that can run shell commands. Node 20 or newer. Bring your own provider keys; the tooling itself costs nothing.

The five artifacts

The workflow is identical every time, and the pieces are where the leverage is:

1. Reference. The video whose format works. It supplies the beats.
2. Brief. What your new video is about. It supplies the content. Keeping reference and brief separate is what makes a format reusable at all.
3. Script. The source of truth: one segment per beat, one or more takes per segment, role cues for speakers. Captions anchor to words in this file, so an edit stays local instead of cascading through a timeline.
4. Media and generation. Assets you already have go in as media items. Anything missing gets declared — and model selection happens here, including your own keys.
5. Run. The agent builds the composition and renders it. Keep --keep when you want intermediates to review, then open the result in Hypit Studio to nudge timing and appearance.

The important detail is that steps 1–3 cost nothing and generate nothing. You spend money only where pixels actually get made, and only if you are not bringing your own keys.

Where it actually pays off

The first clone is the expensive one. You are teaching the agent your format, discovering which beats don't survive translation to your content, and fixing script lines that read fine but sound terrible.

The second clone is cheaper. The third is where it starts printing, because by then you have a format file, a script skeleton and a rendering path — a new video is a script edit and a re-run. This is the honest cost curve of any pipeline: the abstraction is the investment, the variants are nearly free.

One thing worth knowing before you commit to the approach: the format teardown is the hard part, not the render. If you can't describe a video's beats in five lines, no agent will reconstruct it for you.

I keep a running set of format breakdowns, a glossary of the script/track vocabulary, and the full command surface at hypit.video — an independent documentation site for the tool. The step-by-step version lives at hypit.video/guides/how-to-clone-a-video.