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.
npx agentmods add skills/hipson47/hipson/hipson-hyperframes-videonpx skills add Hipson47/Hipson --skill hipson-hyperframes-videogit clone --depth 1 https://github.com/Hipson47/HipsonWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00039 | $0.00972 |
| Opus 5 | $0.00019 | $0.00486 |
| Sonnet 5 | $0.00008 | $0.00194 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
hipson-hyperframes-video 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hipson HyperFrames Video
Use this skill when the user wants a video composition, website-to-video workflow, launch video, product intro, animated case study, pitch video, social short, or rendered MP4-style output using HyperFrames.
Do not merge this workflow into normal web UI design. HyperFrames work is a separate video composition path.
What HyperFrames Is
HyperFrames is a deterministic HTML composition workflow for rendered video. The composition is written as plain HTML/CSS/JavaScript, previewed locally, and rendered to video with Node.js and FFmpeg tooling where available.
Use it when a web-like layout should become a timed video: product launch, feature explainer, changelog recap, case-study animation, pitch asset, or social short.
When Not To Use
- Normal static UI design.
- Backend, API, database, or security-only tasks.
- Pure React component implementation.
- One-off image generation.
- Any task where the user has not asked for video, timeline, render, MP4, or HyperFrames.
Cold Start
When the user only describes the video, ask for or infer:
- audience and goal;
- platform and aspect ratio;
- duration and FPS;
- source copy;
- visual references or brand constraints;
- desired mood;
- audio or silent/caption-first delivery;
- output format and deadline.
Then produce a video brief before implementation.
Warm Start
When the user provides a URL, page, PDF, transcript, changelog, CSV, or copy:
- Extract the story beats.
- Choose what can be shown as text, product UI, chart, screenshot, or motion card.
- Define scenes with timestamps.
- Identify assets that must be local, generated, exported, or omitted.
- Produce a HyperFrames implementation brief.
Core HyperFrames Rules
- Use plain HTML compositions, not React or Vue, unless the user explicitly asks for a framework.
- The root composition element must include
data-composition-id,data-width, anddata-height. - Timed elements use
class="clip",data-start,data-duration, anddata-track-index. - GSAP timelines should be paused and registered on
window.__timelines. - Avoid
Math.random()and async timeline setup. - Keep video elements muted; use separate audio elements.
- Prefer deterministic rendering over live network data or runtime randomness.
- Node.js 22+ and FFmpeg are required for local rendering.
- Use preview, render, and lint commands where available.
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.
- 3d ago First seen · 137 lines · 39 tokens per session scan A 2a8e73b3484c
hipson-hyperframes-video is a skill published in the GitHub repository Hipson47/Hipson (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 972 once invoked, about $0.0002 per session on Opus 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-08-31.
Other skills, from other repositories
deploy
Use when shipping a release of Agent Sessions — bumping version, updating CHANGELOG, building, signing, notarizing, publishing appcast, and creating a GitHub release.
release-notes
Use when writing or curating the user-facing release copy for an Agent Sessions release — README "What's New", GitHub release notes, Sparkle release notes, or website/launch copy. Not for the internal CHANGELOG, which stays a full development history.
sc-skill
Capture deterministic macOS screenshots for testing, docs, release notes, and marketing assets. Use when asked to automate app screenshots, batch-generate screenshot sets, standardize window sizing/composition, or choose between Peekaboo and native macOS screenshot tooling.
add-agent-support
Create and ship AgentSessions support for a new or changed local AI agent/provider. Use when adding, reviewing, testing, documenting, or marketing a provider integration, session parser, transcript source, support-matrix entry, verified-version bump, or provider UI surface; drives the full loop from pre-support…
handover
Use when wrapping up or capturing the current state of a coding session — writes a short, dated entry to the repo's RepoHandover.md so a future agent or you can resume without grepping archived sessions. Triggers on "handover", "hand off", "write handover", "capture state", "checkpoint this session".
agent-session-format-check
Verify agent session format compatibility for Agent Sessions. Use when any agent CLI updates, when monitoring flags drift, or when bumping max verified versions (fixtures + docs + tests). Covers session schema, usage/limits tracking, storage backends, and discovery path contracts for all supported agents.