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/ohad6k/emulo/videonpx skills add ohad6k/emulo --skill videogit clone --depth 1 https://github.com/ohad6k/emuloWrote 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/ohad6k/emulo/video)<a href="https://agentmods.dev/skills/ohad6k/emulo/video"><img src="https://agentmods.dev/badge/skills/ohad6k/emulo/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 | $0.00084 | $0.10631 |
| Opus 5 | $0.00042 | $0.05316 |
| Sonnet 5 | $0.00017 | $0.02126 |
| Haiku 4.5 | $0.00008 | $0.01063 |
Grade A, and why
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 4d 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 — 861 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Emulo video
You take a brief and hand back a film. Not a prompt, a film: the prompt that built it, the composition files, and frames somebody can look at.
0. Load the profile before you write a word
- Locate
emulo.pytwo directories above this skill; fall back to./emulo.pyonly for a direct repo checkout. - Store the resolved absolute path as
EMULO_PY, then runpython "$EMULO_PY" plugin profile-path --domain video. - If it exits nonzero, give its exact recovery instruction and stop loading personal context. Never substitute a generic creative persona.
- Read every returned path completely. First is the core working profile, second is the video profile. Both outrank anything below.
- If the repo has
videos/README.md, it routes short-form work. This skill owns long-form and commercial film only. A vertical Reel that is a designed film, not a screen recording, is this skill.
1. What you hand back
A folder the person can upload to Claude Design and get a film. That is the deliverable. Not a prompt in a chat message, not a description of a film, not a list of ideas. A folder.
Build it at videos/_kits/<brand>/ in this exact shape, because the shape is
what makes it work:
| # | Artefact | Why it is there |
|---|---|---|
| 1 | PROMPT.md |
the brief. One page, in the engine's language |
| 2 | START-HERE.md |
the upload order. Which files, in which order, in one message. Without it the person guesses and the guess is wrong |
| 3 | ATTACH/ |
every asset the film needs, including animations-v3.jsx itself |
| 4 | frames/ |
reference stills whose filenames carry the instruction |
| 5 | KIT.md |
the manifest: every file, its pixel size, its known defects |
Optionally, and only after the four above are finished: build/piece.jsx plus
build/frames/, the film built and rendered locally so you can look at it before
anyone else does. That is verification, not the deliverable. A kit with no local
build still ships. A local build with no kit does not.
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.
- 4d ago First seen · 861 lines · 84 tokens per session scan A 7224bdbf0c77
video is a skill published in the GitHub repository ohad6k/emulo (281 stars, last pushed 10d ago), licensed MIT. It adds 84 tokens to every session and 10,631 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
plur-session-end
Extract durable learnings at the end of a session. Saves corrections, preferences, and codebase patterns as engrams — nothing ephemeral, nothing sensitive.
mnemo-cortex
Installs and wires Mnemo Cortex (local-first persistent memory) into OpenClaw and other MCP-capable agents. Use for cross-session recall, decision history, or multi-agent shared memory.
pre-pr
Prepare a Honcho change for a pull request to plastic-labs/honcho. Invoke before opening a PR, when drafting a PR body, when asked if a branch is PR-ready, or when filling the pull request template. Checks the linked issue, required tests and docs, then writes Description / Proofs / Fixes.
linggen
Linggen — durable cross-host memory plus browser control, over two local MCP servers: ling-mem for memory, the Linggen engine for browser, X and agents. Memory: three-tier model (core + long-term + episodic staging) of who the user is, not a log of what was done; same ling-mem daemon and store in Claude Code, Codex…
remove-meta-narrative
Detect and remove narration of the project's own history from published pages, so a reader gets the current state instead of a draft's changelog. Use before publishing or committing any edit to content/ or site/, when correcting a claim that turned out wrong, when folding a new finding into an existing page, and…
c-03-repo-bootstrap
Bootstrap onboarding for undocumented repos or existing memory slices. Builds root overviews, route-local overview pillars, evidence packs, file cards, onboarding waves, deleted-slice cleanup, curator reviews, and handoff while keeping the orchestrator thin.