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 skills add oyi77/1ai-skills --skill hyperframes-pr-to-videogit clone --depth 1 https://github.com/oyi77/1ai-skillsWrote 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/oyi77/1ai-skills/hyperframes-pr-to-video)<a href="https://agentmods.dev/skills/oyi77/1ai-skills/hyperframes-pr-to-video"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/hyperframes-pr-to-video/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/oyi77/1ai-skills/hyperframes-pr-to-video"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/hyperframes-pr-to-video.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.00084 | $0.00946 |
| Opus 5.5 | $0.00034 | $0.00378 |
| Sonnet 5.5 | $0.00017 | $0.00189 |
| Haiku 4.5 | $0.00008 | $0.00095 |
Grade A, and why
hyperframes-pr-to-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 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This skill turns a pull request diff into a shareable code-walkthrough video via a HyperFrames composition. Use it when a review or announcement benefits from seeing the change animated. It renders an MP4 that presents the PR's story.
HyperFrames — PR to Video
A GitHub pull request → changelog / feature-reveal / fix / refactor explainer. Read via gh CLI, visualized as animated code diffs with narration.
When to Use
- User provides a PR URL (
github.com/owner/repo/pull/123) - User provides a
owner/repo#Nref - User says "this PR" (current branch's PR)
- User wants a feature-reveal video for a merged PR
- User wants a changelog video for a release
When NOT to Use
- User wants a product launch from a website (use
hyperframes-product-launch-video) - User wants a weekly digest (use
hyperframes-changelog-video) - No PR involved (use
hyperframes-faceless-explainer)
Workflow
1 · Fetch the PR
gh pr view 123 --json title,body,files,additions,deletions,author
gh pr diff 123 > pr-123.diff
Extract: title, description, files changed, lines added/removed, author.
2 · Classify the change
- Feature: new files, new functions → feature-reveal arc
- Fix: bug reference, test changes → before/after arc
- Refactor: moved code, no behavior change → simplification arc
- Chore: deps, config → brief mention or skip
3 · Plan the story
- Hook (0-3s): What changed in one sentence
- Context (3-8s): Why it mattered (the problem)
- Diff walkthrough (8-20s): Animated code diff, key hunks highlighted
- Result (20-25s): Before/after, metrics if available
- CTA (25-30s): Link to PR, try it out
4 · Visualize the diff
Render code hunks as styled blocks with line-level highlighting:
<div class="clip diff-scene" data-start="8" data-duration="12" data-track-index="1">
<div class="diff-header">src/auth.ts — +42 / -18</div>
<pre class="diff-added">+ function verifyToken(token) {</pre>
<pre class="diff-removed">- function checkAuth(req) {</pre>
</div>
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 · 103 lines · 84 tokens per session scan A a333c3157e86
hyperframes-pr-to-video is a skill published in the GitHub repository oyi77/1ai-skills (17 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 946 once invoked, about $0.0003 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-10.
Other skills, from other repositories
Release Notes Generator
Generate professional software release notes from a commit log: classify changes, write user-facing summaries, draft a publishable announcement, and assess release readiness. Use for release, changelog, version, and deploy requests.
github-cli
A command-line tool connection for GitHub tasks that built-in tools do not cover. It uses GitHub's command-line program to work with issues, pull requests, releases, workflows, searches, and the GitHub API.
surface-after-care
Regelmäßiger Pflegedurchlauf für ein bereits veröffentlichtes GitHub-Repository (Stufe 1, günstig und oft wiederholbar): zuerst alle Distributionsflächen des Projekts ermitteln (npm, PyPI, Registries, Marketplaces, Stores, Website) und Änderungen später dorthin spiegeln, dann Topics setzen, Privacy-Gate, Dokumente auf…
github-repo-care
Protocol for safely creating, publishing, releasing, auditing, and maintaining GitHub repositories: check local rules and locks, create .gitignore before the first add, run privacy checks, prepare README/i18n/banner/metadata, verify release tags and GitHub releases, and update organization profiles, llms.txt files…
release-engineering
Version, changelog, tag, and publish a release. Use when cutting a release, setting up automated publishing to npm/PyPI/crates.io/Maven/Homebrew, deciding whether a change is major/minor/patch, writing release notes, adopting conventional commits or changesets, planning a 1.0, or handling a bad release that needs to…
launch-and-growth
Get an open-source project in front of the people who need it, and keep them. Use when preparing to announce a project, writing a Hacker News or Reddit or Product Hunt post, planning a launch, writing a blog post about a release, improving GitHub discoverability (topics, About, social preview), or when the user asks…