oh-my-agent is a harness for checking whether coding agents actually completed their work by verifying tests, required artifacts, independent reviews, and recorded decisions. It is used across multiple agent runtimes to make workflow results auditable instead of relying on an agent's own report. The catalogue add-ons provide parts of its skills, agents, hooks, MCP integrations, instructions, and plugins.
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 first-fluke/oh-my-agent --skill oma-videogit clone --depth 1 https://github.com/first-fluke/oh-my-agentWrote 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/first-fluke/oh-my-agent/oma-video)<a href="https://agentmods.dev/skills/first-fluke/oh-my-agent/oma-video"><img src="https://agentmods.dev/badge/skills/first-fluke/oh-my-agent/oma-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/first-fluke/oh-my-agent/oma-video"><img src="https://agentmods.dev/badge/skills/first-fluke/oh-my-agent/oma-video.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00087 | $0.01600 |
| Opus 5 | $0.00044 | $0.00800 |
| Sonnet 5 | $0.00017 | $0.00320 |
| Haiku 4.5 | $0.00009 | $0.00160 |
Grade A, and why
oma-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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- oma-video — 100% identical, 401 lines differ
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Video Router
Scheduling
When to use
Use this skill for a short/reel, README or code explainer, or demo walkthrough.
| Request | Mode | Default aspect | Required source |
|---|---|---|---|
| Short, reel, social clip | shorts |
9:16 |
Topic or brief |
| README, code, data explanation | explainer |
16:9 |
Topic or source path |
| Demo or walkthrough | demo |
16:9 |
Human recording via --capture |
When NOT to use
Use oma-image for a still image, oma-slide for a deck, oma-voice for
audio only, and oma-explanation for an interactive HTML explainer. Editing an
existing finished video and live streaming are out of scope.
Structural Flow
Inputs are a brief plus optional mode, aspect, locale, captions, visual, voice,
music, duration, compositor, capture path, and seed. Outputs live in
.agents/results/videos/<timestamp>-<shortid>-<mode>/:
script.json,timing.json, andrender-spec.jsonform the deterministic asset bus.- Captions and acquired audio/visual assets are recorded in
manifest.jsonwith hashes, providers, cost, warnings, and exit code. - A successful real render contains
<mode>-<slug>.mp4, an encoded video stream, and a positive ffprobe duration.
OMA_VIDEO_MOCK=1 is a test harness only. It can create deterministic text
placeholders with an .mp4 name; those files are never a user deliverable. A
missing Remotion/MPT toolchain, an un-authored composition, a render error, or
an invalid video fails with diagnostics and leaves the script/render spec for
recovery.
Decide and confirm
Infer mode when clear: short/reel -> shorts; README/code/data/explain ->
explainer; demo/walkthrough/capture -> demo. For a one-line request, state
the inferred mode, aspect, duration, visual strategy, captions, locale, and
voice/music before invoking. Do not make the user complete a questionnaire
when those defaults are clear.
Ask only when it changes the result: an ambiguous mode/source, a required demo recording, or a cost confirmation. Respect an explicit mode, aspect, duration, captions, or voice verbatim.
What ships with it
14 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.
- config/video-config.yaml 1.8 KB
- resources/checklist.md 2.3 KB
- resources/execution-protocol.md 7.9 KB
- resources/mpt/driver.py 12 KB runs code
- resources/prompt-tips.md 4.5 KB
- resources/remotion-authoring/demo.md 975 B
- resources/remotion-authoring/explainer.md 901 B
- resources/remotion-authoring/README.md 2.9 KB
- resources/remotion-authoring/shorts.md 1.1 KB
- resources/script-schema.md 3.5 KB
- resources/strudel/package.json 464 B
- resources/strudel/page.html 3.0 KB
- resources/strudel/render.mjs 9.8 KB runs code
- resources/vendor-matrix.md 6.3 KB
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.
- yesterday Changed · -173 lines · -70 tokens per session 7bb365dc9afa
- 4d ago Changed · -2 lines · -6 tokens per session 13bc4cc6d895
- 11d ago First seen · 334 lines · 163 tokens per session scan A e85e5cc1aca3
oma-video is a skill published in the GitHub repository first-fluke/oh-my-agent (1,283 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 1,600 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
scroll-video
Build the foundation of an Apple-style scroll-driven video website — extract frames from a video, render them on canvas, and bind playback to scroll progress with a circle-wipe hero reveal.
motion-animations
Use when building website animations, scroll effects, entrance reveals, layout transitions, gesture interactions, parallax, hero choreography, or any animated UI component. Auto-trigger on any website build or frontend feature that involves motion, transitions, or animated elements.
professional-media-prompts
A prompt-writing workflow for creating detailed image and video instructions for visual assets, storyboards, character sheets, and reference-based generation. It organizes identity, composition, action, camera, timing, and sound requirements.
visual-asset-design
A guide for turning character, scene, and prop ideas into prompts for generating consistent reference images. It covers layouts, camera views, visual identity, and continuity across image variations.
edu-math-tutorial
A Chinese-language guide for turning a maths problem into a step-by-step teaching video. It explains how to break down the solution, write narration, format equations, and structure scenes.
xhs_note
A workflow for creating a Xiaohongshu post, a Chinese image-first social-media note, with short copy, hashtags, and at least three matching vertical images.