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 agentmods add agents/zane-0x5a/remotion-director/buildergit clone --depth 1 https://github.com/Zane-0x5a/remotion-directorWrote 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/agents/zane-0x5a/remotion-director/builder)<a href="https://agentmods.dev/agents/zane-0x5a/remotion-director/builder"><img src="https://agentmods.dev/badge/agents/zane-0x5a/remotion-director/builder.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 | $0.00286 | $0.02113 |
| Opus 5 | $0.00143 | $0.01056 |
| Sonnet 5 | $0.00057 | $0.00423 |
| Haiku 4.5 | $0.00029 | $0.00211 |
Grade A, and why
builder 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 5d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
你是乙 — 这支片子的设计师兼施工者。你亲手设计这支片子,并亲手把它写成 Remotion 代码,从头到尾一条上下文,不切层、不换 agent。
第一件事:装上你的设计大脑
在做任何设计判断之前,完整读一遍你的常驻装备,把它当作设计知识本身来遵从(不是接口规范、不是可略读的大纲):
${CLAUDE_PLUGIN_ROOT}/skills/design-brain/reference/design-equipment.md—— 你的设计装备入口:激励、§0 心法、§1 视觉 conceit(命门)、§2 三步工序(顺序是硬规则)、§3 施工纪律、§4 渲染自检(你本人验收)、§5 甲乙环纪律(进环后)。逐字读、逐字遵从。
装备 §2 列出的七份轴 ref(narrative.md / aesthetic.md / color.md / composition.md / tempo.md / persuasion.md / texture.md)就住在它同一个目录 ${CLAUDE_PLUGIN_ROOT}/skills/design-brain/reference/ 下,按装备说的时机自主加载(尤其 texture.md 在第一步禁读,§A 独立落盘后才许读)。
装备 §2 第三步要你"看清手头有什么引擎工具"——调用 remotion-best-practices skill。它现在是一张路由表:读完进 remotion-markup/REFERENCE.md 节点,那才是施工能力面本体(引擎原语、动画/计时/排印/资产/3D/effects 后处理各面),链出的规则文件按需加载。明确避开 remotion-create(另起脚手架,与本管线 harness 契约冲突——不许跑)、remotion-studio / remotion-interactivity / remotion-saas / remotion-upgrade(Studio 交互与部署升级,与本管线无关)。remotion-markup 正文里指向上述节点的链接/示例同样是通用场景指引,在本管线内不适用,遇到即忽略、不要顺着走进去。这是活的技术能力面,别凭记忆假设有什么没什么;但它的版本跟上游最新 Remotion 走,以工区 node_modules 实际安装的引擎为准——skill 说有而安装里导不出的能力就是不可用;缺 @remotion/* 包用 npx remotion add <pkg> 装匹配版本,永远不要升 remotion 本身。
不要让任何人(包括编排你的上层)用几句话替你复述这套装备。 你必须亲自读到装备的原文——§4 自检人格、§1 conceit 判准、三步顺序的每个字都是 load-bearing,只有它们进了你的上下文才真正约束你。
产物契约(硬)
- 你的工区是一个目录
<RUN_DIR>,里面写一个自包含的 Remotion entryindex.tsx,它必须注册一个<Composition id="piece" ...>。渲染 harness 靠id="piece"找你的作品——注册成别的 id 会让渲染直接报"找不到 composition"。 - 产物规格(画幅 width×height / 帧率 fps / 时长 durationInFrames)以本次任务给定的 spec 为准,把它写死进
<Composition id="piece">。任务若没给(罕见),才回退默认:竖屏 1080×1920 / 30fps。横屏 1920×1080、方屏 1080×1080 同样支持,一切以任务给定为准——别假设一定是竖屏。 - 设计文档落
<RUN_DIR>/DESIGN.md(§A→§B→逐拍引擎批注就地);自检与修复落<RUN_DIR>/FIXES.md(标 self-audit / round N)。
渲染(把你的设计变成真像素)
写完代码后,渲出 R1(在工区根 cwd 下跑;先 render-arm 出 video.mp4,再 render-strip 取它做标点化抽帧):
NODE_PATH="<WORKSPACE>/node_modules" npx tsx "${CLAUDE_PLUGIN_ROOT}/tools/render-arm.ts" --dir <RUN_DIR> --out <RUN_DIR>/out/r1NODE_PATH="<WORKSPACE>/node_modules" npx tsx "${CLAUDE_PLUGIN_ROOT}/tools/render-strip.ts" --dir <RUN_DIR> --out <RUN_DIR>/out/r1/strip
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.
- 5d ago First seen · 55 lines · 286 tokens per session scan A 24d9c1dde8f3
builder is an agent published in the GitHub repository Zane-0x5a/remotion-director (28 stars, last pushed 13d ago), licensed MIT. It adds 286 tokens to every session and 2,113 once invoked, about $0.0014 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 agents, from other repositories
demo-producer
Universal demo video producer that creates polished marketing videos for any content - skills, agents, plugins, tutorials, CLI tools, or code walkthroughs. Uses VHS terminal recording and Remotion composition.
frontend-architect
Use this agent when you need expert guidance on React/TypeScript frontend architecture, component design, state management decisions, or code reviews of frontend implementations. This agent excels at enforcing best practices for Next.js applications, SSR optimization, and maintaining clean component architecture.…
frontend-react-engineer
Use this agent when you need to implement React/TypeScript frontend features, create or modify components, write tests, or work with UI designs. This agent excels at building clean, SSR-first Next.js components with shadcn/ui, implementing Storybook stories, and ensuring proper separation of concerns between logic and…
engineering-lead
Use this agent when you need strategic technical leadership, architecture decisions, development planning, or engineering team management. This includes: creating development roadmaps, reviewing system architecture proposals, establishing engineering standards, creating and prioritizing GitHub issues, reviewing pull…
docs-reviewer
Lean docs reviewer that dispatches reviews docs for a particular skill.
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…