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 BlackBeltTechnology/pi-agent-dashboard --skill beat-sync-videogit clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboardWrote 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/blackbelttechnology/pi-agent-dashboard/beat-sync-video)<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/beat-sync-video"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/beat-sync-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/blackbelttechnology/pi-agent-dashboard/beat-sync-video"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/beat-sync-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.00088 | $0.01134 |
| Opus 5.5 | $0.00035 | $0.00454 |
| Sonnet 5.5 | $0.00018 | $0.00227 |
| Haiku 4.5 | $0.00009 | $0.00113 |
Grade A, and why
beat-sync-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 19d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
beat-sync-video
Input: an approved music-edit/1 from music-edit-to-length. Output:
<stem>_hits.json and a picture edit whose scenes sit on the music grid.
Scripts run in the quick-tier venv (.venv-music); PKG=<this skill dir>/../../...
1. Lock the scene grid
- The composition's root duration = music duration (
durationof_edit.json). - Scene starts come from
downbeats_video— every scene boundary is a downbeat. - Put a scene boundary on each confirmed drop (the drop-aligned boundary): the new scene starts exactly on the drop's video time.
- To land that boundary, compress or stretch the scene before the drop (trim or speed-ramp its shots, drop a shot, or hold the last one) so that it ends exactly on the drop downbeat. Never shift the drop to fit the picture.
2. Pick the hits
.venv-music/bin/python "$PKG/.pi/skills/beat-sync-video/scripts/pick_hits.py" music/track_edit90_edit.json \
[--min-gap 1.5] [--hook-db -30] [--density 7]
- Structural hits: downbeats with the largest 30–150 Hz jump on the edited audio.
One within ±1 downbeat of a confirmed drop (confidence ≥ 0.5) becomes
big, snapped to the drop; the rest aremid. - Hook hits (needs a vocals stem from the deep tier): bars where the vocals bar-RMS
crosses
--hook-dbfrom below. Without stems the script says hook detection was skipped. - Spacing is irregular by construction: a minimum gap (bars), about one hit per
--densityseconds, and a mechanical every-N-bars grid is thinned until ≤ 70 % of intervals are identical. - Hand-placed hits: add
{"t": …, "tier": "big", "source": "manual", "why": "…"}to_hits.json. Manual hits are never thinned and survive every re-run.
music-hits/1: schema, edit (relative path), hits[] {t, tier: big|mid, source: structural|hook|manual, why} sorted by video time, recipe {big, mid}.
3. Punch recipe
| Tier | Scale | y | x | Rotation | Settle | Easing |
|---|---|---|---|---|---|---|
| big | 1.12 | −48 px | ±36 px | 0.8° | 0.6 s | expo.out |
| mid | 1.07 | −28 px | ±18 px | 0.4° | 0.45 s | expo.out |
What ships with it
1 file 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.
- 19d ago First seen · 78 lines · 88 tokens per session scan A 1c71b204e3f4
beat-sync-video is a skill published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (319 stars, last pushed yesterday), licensed MIT. It adds 88 tokens to every session and 1,134 once invoked, about $0.0004 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-27.
Other skills, from other repositories
goga-cookbook
Principles for applying DSL specification in cell and CODEMANIFEST design.
goga-plan-by-design
Compile a design document into a ralphex execution plan.
goga-review-plan
Verify execution plan completeness and correctness.
goga-define-challenge
Challenge the complete product definition before the PRD is generated.
goga-define-project
Understand the current project before defining a product change that must fit into an existing product.
goga-define-requirements
Define the product requirements that describe what the product must do to deliver the established user experience and achieve the agreed product goals.