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 Jerrylalala/compound-engineering --skill feature-videogit clone --depth 1 https://github.com/Jerrylalala/compound-engineeringWrote 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/jerrylalala/compound-engineering/feature-video)<a href="https://agentmods.dev/skills/jerrylalala/compound-engineering/feature-video"><img src="https://agentmods.dev/badge/skills/jerrylalala/compound-engineering/feature-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/jerrylalala/compound-engineering/feature-video"><img src="https://agentmods.dev/badge/skills/jerrylalala/compound-engineering/feature-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.00061 | $0.03651 |
| Opus 5 | $0.00030 | $0.01826 |
| Sonnet 5 | $0.00012 | $0.00730 |
| Haiku 4.5 | $0.00006 | $0.00365 |
Grade A, and why
feature-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 5d 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 feature-video — 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 — 383 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Video Walkthrough
Record browser interactions demonstrating a feature, stitch screenshots into an MP4 video, upload natively to GitHub, and embed in the PR description as an inline video player.
Prerequisites
- Local development server running (e.g.,
bin/dev,npm run dev,rails server) agent-browserCLI installed (load theagent-browserskill for details)ffmpeginstalled (for video conversion)ghCLI authenticated with push access to the repo- Git repository on a feature branch (PR optional -- skill can create a draft or record-only)
- One-time GitHub browser auth (see Step 6 auth check)
Main Tasks
1. Parse Arguments & Resolve PR
Arguments: $ARGUMENTS
Parse the input:
- First argument: PR number, "current" (defaults to current branch's PR), or path to an existing
.mp4file (upload-only resume mode) - Second argument: Base URL (defaults to
http://localhost:3000)
Upload-only resume: If the first argument ends in .mp4 and the file exists, skip Steps 2-5 and proceed directly to Step 6 using that file. Resolve the PR number from the current branch (gh pr view --json number -q '.number').
If an explicit PR number was provided, verify it exists and use it directly:
gh pr view [number] --json number -q '.number'
If no explicit PR number was provided (or "current" was specified), check if a PR exists for the current branch:
gh pr view --json number -q '.number'
If no PR exists for the current branch, ask the user how to proceed. Use the platform's blocking question tool (AskUserQuestion in Claude Code, request_user_input in Codex, ask_user in Gemini):
No PR found for the current branch.
1. Create a draft PR now and continue (recommended)
2. Record video only -- save locally and upload later when a PR exists
3. Cancel
If option 1: create a draft PR with a placeholder title derived from the branch name, then continue with the new PR number:
gh pr create --draft --title "[branch-name-humanized]" --body "Draft PR for video walkthrough"
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.
- 5d ago First seen · 383 lines · 61 tokens per session scan A d57c4fcd40a0
feature-video is a skill published in the GitHub repository Jerrylalala/compound-engineering (5 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 3,651 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to feature-video, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
pr-to-video
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR…
michel-cli-demo-recorder
Produce proof-of-execution demos of the Packmind CLI (packmind-cli) as terminal-styled images (colors and formatting preserved exactly), for embedding in a GitHub PR. Renders a crisp master SVG and rasterizes it to a PNG — the PNG is what you embed, because GitHub does not render SVG in PR/issue bodies. Use this…
pr-to-video
turn a GitHub pull request (a PR URL like github.com/ / /pull/ , an / # ref, or 'this PR' in a checked-out repo) into a code-change explainer video, up to 3 min (sweet spot 30-90s) — changelog, feature reveal, fix, or refactor walkthrough, rendered from the diff / commits / files. The input is a CODE CHANGE read via…
contribute-catalog
Author a new HyperFrames registry block (caption style, VFX block, transition, lower third) or component (text effect, overlay, snippet) and ship it as an upstream PR to the hyperframes repo. Use ONLY when the user wants to CONTRIBUTE to the public catalog — for in-project caption/transition authoring use the…
ozor-changelog-to-video
Convert changelogs, release notes, and version updates into Ozor.ai video prompts. Use this skill whenever the user has a CHANGELOG.md, release notes, GitHub release, version bump summary, or any list of product changes and wants to turn them into a video. Trigger on phrases like 'video from my changelog', 'release…
commit-poet
Turn your git commit messages into poetry. Reads the diff, auto-selects a poem style based on change complexity, and commits with a poetic message. Supports haiku, modern verse, Shakespearean sonnet, and opus (epic formal verse). Triggers on: "commit poet", "poetic commit", "poem commit", "write a poem for my commit".