Borrowing it
Nothing to install: this file belongs to PinkR1ver/vibe-roast. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PinkR1ver/vibe-roast/main/.agents/skills/hyperframes-keyframes/SKILL.mdgit clone --depth 1 https://github.com/PinkR1ver/vibe-roastWrote 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.
[](https://agentmods.dev/skills/pinkr1ver/vibe-roast/hyperframes-keyframes)<a href="https://agentmods.dev/skills/pinkr1ver/vibe-roast/hyperframes-keyframes"><img src="https://agentmods.dev/badge/skills/pinkr1ver/vibe-roast/hyperframes-keyframes/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.
<a href="https://agentmods.dev/skills/pinkr1ver/vibe-roast/hyperframes-keyframes"><img src="https://agentmods.dev/badge/skills/pinkr1ver/vibe-roast/hyperframes-keyframes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00086 | $0.02385 |
| Opus 5.5 | $0.00034 | $0.00954 |
| Sonnet 5.5 | $0.00017 | $0.00477 |
| Haiku 4.5 | $0.00009 | $0.00238 |
Grade A, and why
hyperframes-keyframes 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 1mo 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.
This is a copy
100% identical to hyperframes-keyframes — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HyperFrames Keyframes
Keyframes are a pose contract: visible states, continuous subject identity, seek-safe runtime, verified pixels.
Use hyperframes-animation for broad scene recipes. Use hyperframes-cli for full command docs. Use references/keyframe-patterns.md only when choosing implementation mechanisms, not visual style.
Procedure
- Identify the animated subject, visible states, final state, and runtime.
- Choose the smallest mechanism that proves the prompt. Read
references/keyframe-patterns.mdonly if the mechanism is unclear. - Author seek-safe keyframes in the declared runtime. Build synchronously and register the runtime instance.
- Verify with
hyperframes lint,hyperframes check,hyperframes keyframes, one focused--shot, and snapshots at proof times. - If proof fails, fix the source keyframes and rerun the smallest failing diagnostic before rendering.
Contract
- Name the moving subject.
- Name the poses needed to prove the intended motion, including the final state.
- Keyframe visible channels, not hidden helper state.
- Preserve object identity when continuity matters.
- Crossfade only when the intended motion is replacement or dissolve.
- Hold readable or semantic states long enough to see.
- Final frame is part of the animation, not cleanup.
- Do not reset to rest unless requested.
- Do not end on black unless requested.
- If editing a starter scene, preserve layout, copy, assets, colors, and final state unless asked to redesign.
Runtime Rules
GSAP:
- build synchronously at page load
- use
gsap.timeline({ paused: true }) - register as
window.__timelines[compositionId] - registry key must match
data-composition-id - do not call
tl.play()for render-critical motion - keep repeats finite
CSS keyframes:
- finite duration and iteration count
- deterministic delay
animation-fill-mode: both- use
data-startwhen timing belongs to a clip
Anime.js:
- create synchronously
autoplay: false- finite duration and loops
- push every instance to
window.__hfAnime
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 230 lines · 86 tokens per session scan A 4577193cca20
hyperframes-keyframes is a skill published in the GitHub repository PinkR1ver/vibe-roast (47 stars, last pushed 8d ago), licensed MIT. It adds 86 tokens to every session and 2,385 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to hyperframes-keyframes, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
money
Skill "money" from Hmbown/Codewhale, covering money, when to use, setup, workflow and non-goals.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.