hyperframes-cli

hyperframes-cli is a skill for Claude Code, Codex from jxoesneon/Ciel. It costs 135 tokens per session (4,536 once invoked), scanned A, original, Apache-2.0.

A command-line workflow for building, checking, previewing, rendering, and publishing HyperFrames projects. A command-line tool is a program operated by typing commands in a terminal.

In plain words
What is it for?
Use it to start projects, find reusable effects, lint and test compositions, capture previews, render videos, compare results, and publish them.
Why use it?
It puts the main project tasks in one documented loop and helps inspect or validate a composition before rendering it as video.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to start projects, find reusable effects, lint and test compositions, capture previews, render videos, compare results, and publish them.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jxoesneon/ciel/hyperframes-cli
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add jxoesneon/Ciel --skill hyperframes-cli
Clone the repo
git clone --depth 1 https://github.com/jxoesneon/Ciel

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for hyperframes-cli

README.md
[![agentmods](https://agentmods.dev/badge/skills/jxoesneon/ciel/hyperframes-cli/github.svg)](https://agentmods.dev/skills/jxoesneon/ciel/hyperframes-cli)
Your own site
<a href="https://agentmods.dev/skills/jxoesneon/ciel/hyperframes-cli"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/hyperframes-cli/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for hyperframes-cli

Your own site · 80×15
<a href="https://agentmods.dev/skills/jxoesneon/ciel/hyperframes-cli"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/hyperframes-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 135 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,536 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00135 $0.04536
Opus 5.5 $0.00054 $0.01814
Sonnet 5.5 $0.00027 $0.00907
Haiku 4.5 $0.00014 $0.00454

Measured 4d ago against content hash 9d139dc7c38d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

hyperframes-cli scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/hyperframes-cli/SKILL.md · 185 lines

How it starts

The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plugin installs: Before setup or freshness commands, follow plugin execution rules when this skill is inside a HyperFrames plugin. Standalone installs keep the update instructions below.

HyperFrames CLI

Run commands as npx hyperframes ... unless project instructions provide a wrapper. Obey the wrapper when present. The CLI requires Node.js 22 or newer and FFmpeg.

Development loop

  1. Scaffold: npx hyperframes init <project> (centered blank). Or capture a site. Pass --example=<name> only to start from a named example.
  2. Find the move: if the request names an asset, sound, image, voice or fast visual edit, resolve it through /media-use before proposing a plan. Otherwise, before authoring motion by hand, search for a primitive that already does it: npx hyperframes catalog --query "reveal a headline one line at a time". Ask for the effect you want rather than the mechanism you have in mind. Install with npx hyperframes add <name> (see /hyperframes-registry). Author by hand only once nothing fits.
  3. Author: write the composition using /hyperframes-core. To know what is on a project's timeline (tracks, clips, starts, ends, what plays), run npx hyperframes timeline --json instead of reading index.html and every sub-composition file: nested rows carry absolute main-timeline absStart/absEnd and their owning file, not just their local, per-sub-composition time. Prefer --json over the text form; it costs fewer tokens for the same or better correctness. See references/upgrade-info-misc.md for one-liners that answer common questions without reading the whole output.
  4. Get fast feedback while editing: run npx hyperframes lint after the first HTML pass and after structural changes.
  5. Run the final gate: run npx hyperframes check; it reruns lint before opening the browser. Do not prepend a redundant standalone lint invocation. Add --snapshots for annotated overview frames and finding crops.
  6. Inspect sub-compositions: when index.html mounts data-composition-src, capture midpoint snapshots and inspect each mounted scene.
  7. Open the final Studio preview: run npx hyperframes preview --background, verify the URL returns HTTP 200, hand the timeline project URL to the user, and ask whether to revise or render. Keep it alive until review ends.
  8. Render only after approval: use --quality draft while iterating, --quality looks for the first real encode (the CLI default), and --quality delivery for final delivery.
  9. Verify the output: confirm the file exists and is non-empty. Read the render summary's second line (beginframe vs screenshot, GPU, stage timings). screenshot + software gpu on Linux is the slow path. ffprobe -v error -show_format -show_streams and compare duration (and fps if the brief set it) to the root data-duration.

Read the full file on GitHub · 185 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago Changed 9d139dc7c38d
  2. 12d ago First seen · 185 lines · 135 tokens per session scan A 6065d832ef35

Subscribe to this mod's changes

hyperframes-cli is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 135 tokens to every session and 4,536 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-30.

Related

Other skills, from other repositories

Code Quality Review

Conduct a comprehensive code quality review focused on clean code, architecture, and project standards.

asap-protocol/asap-protocol · 21 tokens

surge

Use when a user provides a PRD, spec, or detailed requirements document and needs a full project delivered through iterative expert orchestration — multi-round analyze/research/design/implement/QA cycles with convergence detection. NOT for: single-file edits, quick prototypes, simple Q&A, or tasks without a written…

carbonshow/intent-fluid · 66 tokens

ai-native-software-dev

Use when the user asks to build, change, modernize, or reconstruct non-trivial software with an AI-native workflow, including greenfield development, work in an existing codebase, or authorized reference-based product reconstruction; also use when lifecycle planning, architecture, implementation, testing, review…

carbonshow/intent-fluid · 101 tokens

redpolicy-guide

An editorial policy for turning webinar transcripts into self-contained guides. A transcript is a written record of spoken material, while a self-contained guide can be understood without watching the webinar.

mikeshu2001/content-factory · 49 tokens

expert-redteam-review

Use when a user asks to evaluate a complex, high-impact, ambiguous, cross-functional, or hard-to-reverse decision; mentions expert panel, red team, adversarial review, rebuttal, judge, arbitration, risk review, challenge assumptions, poke holes, or wants stronger decision quality than a normal review.

carbonshow/intent-fluid · 67 tokens

boil-ocean

Use when the user hands over a big multi-sprint task to finish end-to-end without supervision — "build the whole spec", "implement it all", "do all the sprints", "boil the ocean", "take the decisions yourself", "don't stop until it's done" — or when resuming an existing run (.ocean/state.json exists in the repo, or…

rajkaria/boil-the-ocean · 94 tokens