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 mnvsk97/eyeroll --skill video-to-skillgit clone --depth 1 https://github.com/mnvsk97/eyerollWrote 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/mnvsk97/eyeroll/video-to-skill)<a href="https://agentmods.dev/skills/mnvsk97/eyeroll/video-to-skill"><img src="https://agentmods.dev/badge/skills/mnvsk97/eyeroll/video-to-skill/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/mnvsk97/eyeroll/video-to-skill"><img src="https://agentmods.dev/badge/skills/mnvsk97/eyeroll/video-to-skill.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.00035 | $0.00442 |
| Opus 5 | $0.00017 | $0.00221 |
| Sonnet 5 | $0.00007 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
video-to-skill 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 11d 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
Video to Skill
Watch a tutorial or demo video and generate a Claude Code skill from it.
When To Use
- User says "create a skill from this", "make this into a skill", "turn this into a command"
- User shares a tutorial video and wants to automate the workflow shown
Workflow
- Run
/eyeroll:watch <source> --context "create a skill from this" - Check the report metadata before generating anything:
- Continue when
intentis tutorial/how-to, feature demo, or a workflow walkthrough - Pause and summarize instead when the video is a bug report, question, docs lookup, or general notes
- Continue when
- From the report, identify:
- What workflow/process is demonstrated
- What commands/tools are used
- What inputs and outputs
- Trigger phrases (when should this skill activate)
- Check if
skills/directory exists, read existing skills for patterns - Generate SKILL.md using the template below
- Ask the user to review before finalizing
SKILL.md Template
---
name: {skill-name}
description: >
{What this skill does and when to use it.}
---
# {Skill Name}
{One-liner description.}
## When To Use This Skill
{Bullet list of trigger conditions.}
## Workflow
{Numbered steps the agent should follow.}
## Example Interactions
{2-3 realistic examples.}
## Rules
{Guardrails and constraints.}
Rules
- Always run
/eyeroll:watchfirst — don't generate a skill without understanding the video - Do not force every video into a skill; use the report intent and handoff recommendation to decide
- Keep SKILL.md under 500 lines
- The generated skill should be self-contained
- Ask the user to review before finalizing
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.
- 11d ago First seen · 70 lines · 35 tokens per session scan A 7caae44dac60
video-to-skill is a skill published in the GitHub repository mnvsk97/eyeroll (17 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 442 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-30.
Other skills, from other repositories
write-test-plan
Generate a QA/UAT test plan from product specifications and task definitions, covering acceptance testing, integration flows, and exploratory testing. Unit tests are out of scope (handled by write-unit-tests skill).
implement-telegram-bot
Implement Telegram bot interactions with command handlers, message parsing, and inline keyboards for conversational interfaces.
setup-background-job
Set up scheduled background jobs using Quartz.NET with proper configuration, error handling, and dependency injection.
write-unit-tests
Write comprehensive unit tests with proper setup, assertions, and coverage of happy paths, edge cases, and error scenarios.
auto-improve
GAN-style iterative improvement loop for any text artifact. Mutates a file, grades each change against a rubric with a SEPARATE model, keeps only verified wins (pairwise-judged), reverts the rest. The git history is the improvement log. Use when the user wants to autonomously improve the quality of a document, email…
blazor-component-design
Design Blazor components with proper parameter binding, event callbacks, lifecycle management, and render optimization. Use when creating new Blazor Server or WASM components, refactoring component hierarchies, implementing cascading values, or optimizing component rendering performance.