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 gowtham012/Claude-plugins --skill build-from-videogit clone --depth 1 https://github.com/gowtham012/Claude-pluginsWrote 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/gowtham012/claude-plugins/build-from-video)<a href="https://agentmods.dev/skills/gowtham012/claude-plugins/build-from-video"><img src="https://agentmods.dev/badge/skills/gowtham012/claude-plugins/build-from-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.00040 | $0.00315 |
| Opus 5 | $0.00020 | $0.00158 |
| Sonnet 5 | $0.00008 | $0.00063 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
build-from-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 7d 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.
What it actually says
Build frontend from video: $ARGUMENTS
Arguments:
$0= video_path (required)$1= framework:reactorhtml(default:react)$2= output_dir (default:./output)
Steps
-
Call MCP tool
mcp__video-insight__build_frontend_from_videowith:video_path=$0framework=$1if provided, elsereactoutput_dir=$2if provided, else./output
-
The tool returns
files_created,scene_count,framework. Read the generated files and display them. -
Provide a brief summary:
- UI components generated
- Scenes that contributed most content
- Sections where OCR text or transcript filled in exact copy
- Suggested next steps (routing, API connections, etc.)
Output files
React: App.jsx + App.css
HTML: index.html (self-contained, inline CSS + JS)
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.
- 7d ago First seen · 35 lines · 40 tokens per session scan A b3fce2b6687d
build-from-video is a skill published in the GitHub repository gowtham012/Claude-plugins (5 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 315 once invoked, about $0.0002 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
layout-patterns
Common UI layout patterns using fundamental-styles - login forms, dashboards, master-detail, wizards, and more.
component-composition
How to combine fundamental-styles components correctly - required wrappers, nesting rules, and common composition patterns.
interface-craft
Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered product from a generic one. Use this when a screen works but looks unfinished or default, when a layout feels crowded or arbitrary, when a page has no clear focal point, or…
bem-naming
BEM (Block Element Modifier) methodology and naming conventions used in fundamental-styles with real examples.
design-system
Builds and maintains the design system a product is assembled from — tokens for color, type, spacing and elevation, component contracts, and the rules that keep them coherent as the product grows. Use this when starting a new interface, when screens have drifted apart visually, when the same component exists three…
component-docs
Browse fundamental-styles component documentation with complete HTML examples from 140+ auto-generated markdown files. Use this when the user asks about component examples, modifiers, variants, HTML structure, or wants to see working code for any fundamental-styles component (button, table, input, dialog, etc.). Also…