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 Cypsy1714/cchad --skill remotion-skillgit clone --depth 1 https://github.com/Cypsy1714/cchadWrote 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/cypsy1714/cchad/remotion-skill)<a href="https://agentmods.dev/skills/cypsy1714/cchad/remotion-skill"><img src="https://agentmods.dev/badge/skills/cypsy1714/cchad/remotion-skill.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.00026 | $0.00303 |
| Opus 5 | $0.00013 | $0.00151 |
| Sonnet 5 | $0.00005 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
remotion-conventions 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
Remotion conventions
Guidance for building maintainable programmatic video with Remotion.
Compositions
- Register each video as a
<Composition>with explicitdurationInFrames,fps,width, andheight. Keep these in one constants file. - Drive everything from props so the same composition renders many variations.
Timing
- Treat frames as the unit of time. Convert seconds with
fps(seconds * fps) rather than hard-coding frame numbers. - Read the current frame with
useCurrentFrame()and animate withinterpolate()/spring(). Keep animation math pure and frame-driven so every render is deterministic. - Clamp
interpolatewithextrapolateLeft/Right: "clamp"to avoid values running past their range.
Structure
- Build small presentational components (a title, a lower-third, a transition)
and compose them in a sequence with
<Sequence>. - Offset timing with
<Sequence from={…}>instead of branching on the frame number inside a component.
Rendering
- Keep assets deterministic: use
staticFile()for bundled media and avoid randomness that isn't seeded. - Render from the CLI (
npx remotion render) in CI so output is reproducible.
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 · 34 lines · 26 tokens per session scan A 125e57bc74fb
remotion-conventions is a skill published in the GitHub repository Cypsy1714/cchad (1 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 303 once invoked, about $0.0001 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
artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
remotion
Render a short (10s) video on any topic with Remotion - the agent writes a storyboard JSON, a bundled React/Remotion project renders it to an MP4, and the clip is committed to the repo and delivered by URL. No editor, no external generative API.
react-expert
Use when working in a React 19 / Next.js 15 codebase - .tsx/.jsx files, next.config.ts, app/ router directories, "use client"/"use server" directives, package.json with react or next dependencies. Builds and refactors Server/Client Components, server actions and forms, Suspense/streaming UIs, and TanStack Query or…
remotion-agent-video
Remotion v4.0.4xx with agent skill support for AI-driven video creation. Covers programmatic video generation with React, the new effects ecosystem, and first-party agent skills.
senior-frontend
Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.
nextjs-ssr-patterns
Default command for population on a fresh worktree or after a git pull that includes a lockfile change: npm ci — lockfile-respecting, deterministic install. Run from the project root. This is the form CI workflows and Dockerfiles use. The bare npm install form is acceptable only when the lockfile is known-stale or for…