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 floomhq/moto --skill yc-videogit clone --depth 1 https://github.com/floomhq/motoWrote 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/floomhq/moto/yc-video)<a href="https://agentmods.dev/skills/floomhq/moto/yc-video"><img src="https://agentmods.dev/badge/skills/floomhq/moto/yc-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/floomhq/moto/yc-video"><img src="https://agentmods.dev/badge/skills/floomhq/moto/yc-video.svg" alt="Reviewed on agentmods" width="80" 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.00088 | $0.02820 |
| Opus 5 | $0.00044 | $0.01410 |
| Sonnet 5 | $0.00018 | $0.00564 |
| Haiku 4.5 | $0.00009 | $0.00282 |
Grade A, and why
yc-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 6d 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YC Video Skill
Plan, build, audit, and score startup launch videos that convert cold social feeds.
Three Modes
| Mode | When | Command |
|---|---|---|
| Plan | Starting a new video | /yc-video plan |
| Score | Evaluating an existing video | /yc-video score <path> |
| Audit | Deep qualitative review | /yc-video audit <path> |
Mode 1: Plan
Step 1: Define the constraints
Collect from user or infer:
- Duration: 15s (teaser), 30s (explainer), 60s (demo)
- Format: Square (1080x1080, LinkedIn/X autoplay) or Wide (1920x1080, YouTube/X)
- Audio: Muted-first (captions carry the story) or VO-driven
- Platform: LinkedIn, X, YouTube, Product Hunt
- Audience temperature: Cold (never heard of you) or Warm (waitlist, followers)
Step 2: Apply the 3-Act Structure
Every YC-grade launch video follows this arc:
ACT 1: PAIN (0-3s)
Statement of a problem the VIEWER has felt.
Not your metric. Not your product. Their frustration.
Must work in silent autoplay (text on screen).
ACT 2: BRIDGE + FLOW (3-10s)
"What if..." or "So I built..." transition.
One continuous product demonstration.
NOT feature list. One fluid action: input -> magic -> output.
The product is the hero. Show, don't tell.
ACT 3: PROOF + CLOSE (10-15s)
Social proof, metric, or "aha" reveal.
Logo + CTA + URL.
This is where your impressive number lives (not second 1).
Step 3: Write the shot list
For each second, define:
- Visual (what's on screen)
- Text overlay (what the muted viewer reads)
- VO line (if applicable)
- Animation (entry, emphasis, exit)
Use this format:
| Time | Visual | Caption | VO | Animation |
|------|--------|---------|----|-----------|
| 0-1s | Dark bg, pain text | "You apply to 50 jobs." | -- | Fade from black, type-on |
| 1-3s | Pain continued | "Hear back from 2." | -- | Beat pause, then type |
| 3-4s | Product appears | "What if jobs found you?" | "What if..." | Slide up from bottom |
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.
- 6d ago First seen · 282 lines · 88 tokens per session scan A 44d0de7aed9e
yc-video is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 3mo ago), licensed MIT. It adds 88 tokens to every session and 2,820 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-09-03.
Other skills, from other repositories
memstack-content-youtube-script
Use this skill when the user says 'YouTube script', 'video script', 'write script for YouTube', 'YouTube video outline', or is creating scripted content for a YouTube video with hooks, chapters, and CTAs. Do NOT use for TikTok/Reels short-form scripts or webinar presentations.
memstack-marketing-facebook-ad
Use this skill when the user says 'facebook ad', 'FB ad', 'Meta ad', 'Instagram ad', or needs social media ad copy with targeting, creative direction, and A/B test plans for Meta Ads Manager. Do NOT use for Google search ads or organic social content.
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
self-assessment
Interactive skill assessment with personalized learning path generation.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.