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 krzysztofsurdy/code-virtuoso --skill video-productiongit clone --depth 1 https://github.com/krzysztofsurdy/code-virtuosoWrote 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/krzysztofsurdy/code-virtuoso/video-production)<a href="https://agentmods.dev/skills/krzysztofsurdy/code-virtuoso/video-production"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/video-production/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/krzysztofsurdy/code-virtuoso/video-production"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/video-production.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.00067 | $0.02299 |
| Opus 5.5 | $0.00027 | $0.00920 |
| Sonnet 5.5 | $0.00013 | $0.00460 |
| Haiku 4.5 | $0.00007 | $0.00230 |
Grade A, and why
video-production 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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Video production
Asked for a video, an agent usually starts coding in the engine it knows best, renders the whole film to find out whether it looks right, bolts audio on at the end, and delivers a file nobody checked. Each of those costs a full render cycle or a rework. This playbook puts the cheap decisions first (engine, storyboard, numbers), checks work with single frames before any full render, and treats sound as part of the film.
It is the workflow. The craft rules for timing, easing, type, safe areas, flashing and caption layout live in the motion-design skill: load it before the spec step and do not restate its numbers here.
Principles
| Principle | Why |
|---|---|
| Approve stills before code | A drawn frame is cheap to change. A built scene is not |
| Every adjective becomes a number | "Snappy" and "calm" cannot be checked. Seconds, frames, pixels and percentages can |
| Look before you render | A frame capture takes seconds. A full render takes minutes and hides which frame is wrong |
| Time belongs to the engine | Anything driven by a wall clock, a CSS transition or a network call renders differently each run |
| Audio sets the clock | Narration or music length decides shot length. Shots stretched to fit a voice later never feel right |
| Show real things | Use the real product screens, logo and data. Draw or generate only what has no source |
| Say what you could not check | An agent cannot hear or watch the film. Measure what can be measured and list the rest |
Workflow
Eight steps. Each ends with a gate. Do not start the next step before the gate passes.
1. Brief
Read the request and the project (existing video code, brand files, assets folder) first. Ask only for what is missing, in one batch. Details and the brief template are in storyboard-and-spec.
Needed: the one thing the viewer should do or remember, audience, platform and aspect ratio, length, narration or music or silence, source assets, brand tokens, languages, and whether the result is for commercial use.
What ships with it
6 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.
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 First seen · 131 lines · 67 tokens per session scan A 54206f47c3a2
video-production is a skill published in the GitHub repository krzysztofsurdy/code-virtuoso (36 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 2,299 once invoked, about $0.0003 per session on Opus 5.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-10-23.
Other skills, from other repositories
hermes-diagnostic-review
Use when running a read-only diagnostic review of recent Hermes sessions to find recurring mistakes, failed tool calls, and repeated fixes, then propose suggestion-only improvements and reusable skills. Human-gated; never auto-applies.
instruction-eval
Change one condition an agent runs under (instruction text, the reference material instructions point at, MCP tools and permissions, hooks, skill files), then run the same prompts before and after, several times each, to see what actually changes. Produces an HTML report showing both arms' answers side by side. Use…
worth-building
Decide how elaborate to build something (simple vs. robust) and return a concrete, PoC-shaped proposal at that level — not over- or under-engineered, but right-sized. Use whenever someone is building something and the investment level is unclear: "quick or proper?", "MVP vs. real product", "is this over-engineering?"…
django-ticket-triage
Analyze a Django Trac ticket and produce a triage recommendation report — duplicate search, related PRs, forum threads, and the affected source code. Use when the user gives a Django ticket number, or asks whether a ticket is valid, a duplicate, or ready for a triage stage.
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
healthcheck
Host security hardening and risk-tolerance configuration for OpenClaw deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, or version status checks on a machine running OpenClaw (laptop, workstation, Pi, VPS).