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 bravew/trove --skill trove-beat-syncgit clone --depth 1 https://github.com/bravew/troveWrote 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/bravew/trove/trove-beat-sync)<a href="https://agentmods.dev/skills/bravew/trove/trove-beat-sync"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-beat-sync/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/bravew/trove/trove-beat-sync"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-beat-sync.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.00062 | $0.01010 |
| Opus 5.5 | $0.00025 | $0.00404 |
| Sonnet 5.5 | $0.00012 | $0.00202 |
| Haiku 4.5 | $0.00006 | $0.00101 |
Grade A, and why
trove-beat-sync 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 8d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beat-synced timelines
Use this skill when a chosen music track should shape a video timeline. Analyze and accept the beat grid before storyboarding. If no track is chosen, pace the edit to its content and leave beat sync for later. Defer media measurements and normalization to trove-ffmpeg.
Measure and accept the grid
scenes.py --beatsrequires a video stream, so it cannot read an audio-only track directly. For an audio-only track, first get consent to create temporary media. Usebackground.pyto make a silent carrier at least as long as the track, thenaudio.py --replaceto add the track. Read the installed manual for file arguments. Runscenes.py ANALYSIS_VIDEO.mp4 --beats. Do not claim direct MP3 support.- Record BPM, phase, onset count, supported-beat count, confidence, and
usablefrom the result. Check likely half-time and double-time interpretations against supported onsets. Do not choose a tempo from the scalar alone. - Apply the acceptance gate in Beat analysis.
usable: trueis necessary, but it does not prove every residual criterion. Do not claim match or residual limits passed unless measured evidence provides them. - If the gate fails or the grid remains uncertain, ask before running
uv run --with librosa --with scipy --python 3.11. State that the command downloads packages. Without consent, report the measured result and use content pacing. Do not quietly install, download, or substitute another package. - When
trove-ffmpegis unavailable, mark grid analysis and dependent checks unchecked. Do not invent command output.
Build the timeline
Keep source phase and beat interval in floating-point seconds. Convert to frames only when writing the Remotion timeline. Use one shared beatF(n) function for beat-anchored cuts and keyframes. Keep source phase unchanged when compensating output offset. The formula and an example are in Beat analysis.
What ships with it
3 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.
- 8d ago First seen · 46 lines · 62 tokens per session scan A ab52d27a4561
trove-beat-sync is a skill published in the GitHub repository bravew/trove (10 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 1,010 once invoked, about $0.0002 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-10-09.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…