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 danielrosehill/Claude-AI-Video-Producer-Plugin --skill upscale-and-interpolategit clone --depth 1 https://github.com/danielrosehill/Claude-AI-Video-Producer-PluginWrote 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/danielrosehill/claude-ai-video-producer-plugin/upscale-and-interpolate)<a href="https://agentmods.dev/skills/danielrosehill/claude-ai-video-producer-plugin/upscale-and-interpolate"><img src="https://agentmods.dev/badge/skills/danielrosehill/claude-ai-video-producer-plugin/upscale-and-interpolate/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/danielrosehill/claude-ai-video-producer-plugin/upscale-and-interpolate"><img src="https://agentmods.dev/badge/skills/danielrosehill/claude-ai-video-producer-plugin/upscale-and-interpolate.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.00034 | $0.00493 |
| Opus 5 | $0.00017 | $0.00246 |
| Sonnet 5 | $0.00007 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
upscale-and-interpolate 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 12d 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
Upscale & Interpolate Pipeline
Post-processing for clips that need higher resolution or frame rate than the generation model produced.
When to use
- Generation model output is 720p/1080p but the brief calls for 4K.
- Clip is 24fps but the brief calls for 60fps slow-mo or smoother motion.
- A specific take is great but visibly soft/low-fps.
When NOT to use
- Clip is already at target spec — don't upscale unnecessarily, it adds cost and processing time without benefit.
- Source quality is poor — upscaling amplifies artefacts. Regenerate instead.
Inputs
- A clip in
clips/selected/(orclips/raw/if user wants to upscale before selection). - Target resolution and fps from
brief/creative-brief.md. - Upscale + interpolation models from
brief/tools-and-models.md(e.g. Topaz, Real-ESRGAN, RIFE, FILM).
Steps
- Confirm target. Read brief; state current vs target resolution and fps.
- Upscale. Call configured upscaler. Save to
generation/upscale/NN-shortname-vN-up.mp4. Log it. - Interpolate (if fps target > source fps). Call interpolation model on the upscaled output. Save to
generation/upscale/NN-shortname-vN-up-interp.mp4. Log it. - QC. Show before/after comparison if possible. Watch for: temporal artefacts, ghosting on fast motion, oversharpening haloes.
- Promote. Copy approved final to
clips/edited/NN-shortname-final.mp4.
Common gotchas
- Order matters. Upscale first, interpolate second. Interpolating then upscaling wastes compute on synthetic frames.
- Interpolation breaks on cuts. If a clip contains an internal cut (rare for AI-gen but possible), interpolation will smear across it.
- File size explosion. A 4K/60fps clip is ~4× the size of 1080p/30fps. Plan storage accordingly.
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.
- 12d ago First seen · 40 lines · 34 tokens per session scan A 5a336ac9d32e
upscale-and-interpolate is a skill published in the GitHub repository danielrosehill/Claude-AI-Video-Producer-Plugin (4 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 493 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…