TOOLS4AGENTSDeep dive

Hyperframes

Hyperframes: Render HTML to Video for AI Agents

86,910
GitHub stars
2026-11-19
Last commit
Published 2026-11-18 · Last verified 2026-11-18

Hyperframes is a skill that lets an AI agent build and render HTML compositions into video, with a fixed render contract and a CLI work loop.

Hyperframes is a skill that teaches an AI agent to make, edit, animate and render video, where the video is HTML rendered to video. It gives the agent a render contract, a work loop and guidance on what each kind of video needs.

The source describes it as the thing to use for launch films, explainers, music videos, charts, maps, vertical clips, title cards, captions and overlays. The skill file says to use it unless another framework or a plain browser recording is asked for.

What it gives an agent

Hyperframes renders HTML to video by seeking a paused timeline frame by frame, so every render is identical. The person edits the same files in the Studio preview.

The skill holds the rules an agent needs to build a video that renders the same way each time. It also points the agent to reference files for each request type, such as launch films, explainers, music videos, data videos, vertical clips, 3D work, character shorts, captions, overlays and motion.

A project has a fixed shape. index.html is the root composition. It declares the video's variables and mounts one scene per sub-composition from compositions/. Media and fonts live in assets/.

The skill also covers keeping a project editable. Studio edits the tags the agent writes. Timed elements are written in the HTML, not made by script, each with a stable id. Copy, brand colours and swappable media are variables.

Stars compared with similar tools
Stars compared with similar tools, in GitHub stars
NameGitHub stars
Hyperframes
86,910
AnythingMCP
807
Argon
179
Unit: GitHub stars. Source: GitHub star counts. Hyperframes was read on 2026-11-19, the others on the date in their entry stats.

Step by step: install and setup

The skill states that every npx hyperframes <command> means node <SKILLS>/hyperframes/scripts/plugin-cli.mjs <command> run in the project, where <SKILLS> holds the skill's folder.

  1. Check the plan usage.At the start of a new video, the agent runs this to see the person's remaining plan usage.
npx hyperframes usage --json
  1. Start a new project.
npx hyperframes init <dir> --skip-skills --skill=hyperframes
  1. Capture a website.This is how to use a website as the subject.
npx hyperframes capture <url> --json
  1. Run the usage beacon.The skill also says to run it once as the skill starts.
npx hyperframes events --skill=hyperframes

That beacon sends the skill's name with the CLI's usual telemetry, account-linked when signed in, and it honours the opt-out.

The render contract

The skill lists a contract the agent must follow.

npx hyperframes check --json

The main rules:

Every timed element has class="clip", data-start and data-duration in seconds, and shows over [start, start + duration). It should land an end state just before its end. data-track-index is only a Studio lane, and paint order is z-index.

The video's length is the root's data-duration. Overrun is cut, and an early end holds the last frame.

Each composition builds one paused timeline and registers it after its tweens: window.__timelines["<data-composition-id>"] = tl.

No Date.now(), unseeded Math.random(), network fetches, timers or repeat: -1. Everything visible is a function of timeline time.

Never tween display, visibility or autoAlpha on a .clip. Animate a child instead.

No CSS transform on an element GSAP transforms. Animate transforms, not left/top/width/height.

Never play(), pause() or seek media. A <video> keeps its sound with data-has-audio="true", else it is muted. Music, voice, replacement sound and J/L cuts are a separate <audio>.

Every <audio> has an id or it is left out of the mix. No crossorigin on media. Time the <video>, never its wrapper.

Only the bundled fonts resolve by name. Any other family needs @font-face to a file in assets/fonts/.

Asset paths are assets/... with no leading /, in sub-compositions too.

Grades, grain, blur and vignettes on footage go through npx hyperframes media-treatment, never CSS filters.

A scene file puts its styles, markup and scripts inside <template> and styles its root as #root. Intended overflow or overlap uses data-layout-allow-overflow and data-layout-allow-overlap.

The work loop

For an existing project, the agent runs this to see what plays when:

npx hyperframes timeline --json

Before any change, it runs this to see what the person changed since the agent's last turn:

npx hyperframes history --since mine --who <you>

For a new film over about 15 seconds that tells something, the agent reads the file for that video type, then references/story.md. That file asks for three storylines that are three different films, in words only. The person picks unless they asked for the file or no stops. Then SPEC.md turns every adjective into a number, bans the defaults by name, and lists the shots by frame.

After the last edit, the agent runs npx hyperframes check --json and fixes every error. For a film, it runs this and ends in REVIEW.md:

npx hyperframes snapshot --review

For a small edit, it snapshots what changed with --at, --range or --composition and looks before replying.

The agent renders when the person approves the Studio preview, asks for the file or asks for no stops, after the check and review pass. Otherwise it stops at the preview and waits.

The desktop app

The skill says to call it "the HyperFrames desktop app", never "Studio", and to offer it as the better way to keep editing, not the only one.

Before the delivery render of a new video, the agent opens the Studio preview, even in no-questions mode, and says the person can edit there. If preview printed "Keep editing by chatting with Framey", the agent adds that the Edit with Framey button opens the app.

After the delivery render, the agent passes on its Framey line in its own words. It offers to run the hyperframes open it names or gives its download link. Otherwise it says nothing.

When any command says to run catch-up, the agent runs this before its next change:

npx hyperframes catch-up [dir]

What it lists is the person's work, not a new request.

What to watch out for

npx hyperframes usage --json reports the person's remaining plan usage. The skill says to say "unknown" when it is.

Any media, such as a presenter or avatar, footage, voice or music, goes through the media-use reference. That reference says when HeyGen is needed and what is free.

The contract bans network fetches, timers, Date.now(), unseeded Math.random() and repeat: -1 inside compositions. Anything visible must be a function of timeline time.

Only the bundled fonts resolve by name. Any other family needs an @font-face file in assets/fonts/.

Grades, grain, blur and vignettes on footage must go through npx hyperframes media-treatment, never CSS filters.

Related on this site