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/benyki/gtm-engine/engine-videonpx skills add benyki/gtm-engine --skill engine-videogit clone --depth 1 https://github.com/benyki/gtm-engineWrote 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/benyki/gtm-engine/engine-video)<a href="https://agentmods.dev/skills/benyki/gtm-engine/engine-video"><img src="https://agentmods.dev/badge/skills/benyki/gtm-engine/engine-video.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.1 | $0.00081 | $0.05419 |
| Opus 5 | $0.00041 | $0.02710 |
| Sonnet 5 | $0.00016 | $0.01084 |
| Haiku 4.5 | $0.00008 | $0.00542 |
Grade A, and why
engine-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.
How it starts
The opening of the file, as written. The whole thing — 409 lines — stays where its author put it; the contents beside it link to each section on GitHub.
engine-video
Script to rendered 9:16 mp4. The heaviest engine in the repo — it needs disk, keys and patience — so don't pick it as a first engine unless video is genuinely the channel.
This skill runs any engine folder of type video. The default folder is
video/; paths below (templates/, runs/, inputs/) are inside it, while
brand, accounts, keys and reusable footage/fonts/logos live in shared/
(shared/assets/ — any engine can use them).
Several video engines are the normal shape, one per format, each with its own templates, experiments and metric. Name them after the format they run:
| Folder | Format |
|---|---|
video-app/ |
viral product |
video-vibe/ |
viral vibe |
video-info/ |
informative |
All of them are type video — scaffold one with
--merge --engine video-vibe:video, or copy a folder and empty its runs/
and reports/ (history belongs to the original). Running a single format? Keep
the shipped video/ folder and ignore the rest. Render knobs (resolution,
target_seconds, voice id) live in each folder's engine.json under video,
so two video engines can render differently.
Paths in this file: shared/… means the gtm home (~/gtm by default, or
$GTM_HOME); templates/, inputs/, runs/ and reports/ mean the engine
folder you're running, wherever it lives. The scripts resolve both through
~/gtm/engines.json, so read them as names rather than literal paths.
Three formats, by default
Decide which one you're making before anything else — it sets the length,
the footage, whether there's a voice, and how loud the music is. Full spec and
the editorial rules for each: references/formats.md.
| Length | Voice | Music | Copy from | |
|---|---|---|---|---|
| Viral product — 4s hook + ~12s of the product working | ~16s | usually none | 50% | examples/viral-app-demo.json |
| Viral vibe — one meditative clip, two lines of text, product named only in the caption | 8–15s | never | 50% | examples/viral-vibe.json |
| Informative — text content (an article, a dataset, a series) turned into something watchable | 30–60s | ElevenLabs | 3% (optional) | examples/informative-vocab.json, examples/informative-recap.json |
What ships with it
25 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.
- assets/fonts/OFL.txt 4.3 KB
- assets/fonts/TikTokSans12pt-Bold.ttf 165 KB
- assets/fonts/TikTokSans12pt-Regular.ttf 165 KB
- examples/informative-recap.json 6.3 KB
- examples/informative-vocab.json 5.1 KB
- examples/viral-app-demo.json 4.5 KB
- examples/viral-vibe.json 3.5 KB
- references/advanced.md 6.2 KB
- references/clip-sourcing.md 6.7 KB
- references/duplicate-safety.md 6.0 KB
- references/ffmpeg-recipes.md 3.0 KB
- references/ffmpeg-text-style.md 9.5 KB
- references/floating-text.md 2.8 KB
- references/footage-pexels.md 1.9 KB
- references/formats.md 9.8 KB
- references/hook-guide.md 12 KB
- references/looks.md 2.7 KB
- references/music.md 2.9 KB
- references/posting-api.md 2.0 KB
- references/posting-options.md 3.3 KB
- references/remotion.md 1.7 KB
- references/structure-plan.md 3.5 KB
- references/voiceover.md 2.3 KB
- scripts/combo_check.py 6.5 KB runs code
- scripts/text_style.py 10 KB runs code
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 · 409 lines · 81 tokens per session scan A 1c9eb106b877
engine-video is a skill published in the GitHub repository benyki/gtm-engine (5 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 5,419 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…