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 agentmods add skills/ronak-create/fablecut/remake-reelnpx skills add ronak-create/FableCut --skill remake-reelgit clone --depth 1 https://github.com/ronak-create/FableCutWrote 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/ronak-create/fablecut/remake-reel)<a href="https://agentmods.dev/skills/ronak-create/fablecut/remake-reel"><img src="https://agentmods.dev/badge/skills/ronak-create/fablecut/remake-reel.svg" alt="Measured on agentmods" 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 | $0.00074 | $0.00667 |
| Opus 5 | $0.00037 | $0.00333 |
| Sonnet 5 | $0.00015 | $0.00133 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
remake-reel 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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remaking a reference edit
Given a video the user likes, FableCut extracts what is measurable about the edit — where the cuts land, where the beats are, how energy moves — and hands it back as a blueprint. The structure is deterministic; the creative mapping onto new footage is yours.
Get the blueprint
fablecut_analyze_reference {path:"C:\\…\\ref.mp4"}
Needs ffmpeg on PATH. It returns shot boundaries (cuts, shots[] with a
per-shot energy 0–100), music beats[] and bpm, a loudness energy curve,
and drop — the biggest musical rise. It also extracts the reference's music
track into the project and registers it as media, so the rebuild can sit on the
same song.
If obvious cuts were missed, lower threshold; if camera motion is being read
as cuts, raise it.
Rebuild
- Match the canvas: copy the reference's
width/height/fpsonto the project. Writebeatsintomarkersso the user can see the grid and the UI snaps drags to it. - Music on A1,
in: 0, running the full reference duration. - One clip per
shots[]entry on V1 at the samestartandduration. Match footage to each shot'senergy— calm material under ~40, motion over ~70 — and choose each clip'sinso something actually happens inside the window. - Land the hero shot on
drop. The standard garnish is a speed ramp settling into it, anadjustlayer withshake+rgbSplitfor one impact frame, or a whip transition on the way in. - Pace to taste: shots under ~0.6 s read as beat-flashes.
avgShotLentells you the reference's overall rhythm.
Full recipe, including the exact keyframe shapes for speed ramps and impact
layers: fablecut_docs {section:"Remake a reference video"} and
fablecut_docs {section:"Recipes"}.
Be honest about what this does
The blueprint captures structure — timing, pacing, where the energy sits. It does not capture look, subject, or performance. Tell the user that a rebuild matches the rhythm of the reference and that the grade, footage, and titles are separate choices, rather than implying the result will look like the original.
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 · 56 lines · 74 tokens per session scan A 84e48b484850
remake-reel is a skill published in the GitHub repository ronak-create/FableCut (653 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 667 once invoked, about $0.0004 per session on Opus 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-08-30.
Other skills, from other repositories
browse
Use the browse CLI for Browserbase browser automation, Browserbase cloud APIs, Browserbase Functions, templates, web fetch/search, diagnostics, and Browse.sh skill discovery/installation. Use when the user asks to navigate pages, inspect browser state, run local or remote browser sessions, manage Browserbase…
sanity-check
Run the deferred AgentOS E2E smoke test from public npm packages. Use when the user asks to sanity check, smoke test, or verify a release works.
release
Cut an AgentOS release via the scripts/publish flow. Use when the user asks to release, publish, cut a release, or bump the AgentOS version.
launch-graphics
Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.
release-preview
Cut an AgentOS release-preview. Use when the user asks for a preview, release-preview, or a branch dist-tag build.
publish-registry
Publish @agentos-software/ registry packages from AgentOS. Use whenever the user asks to publish or release registry software/agent packages.