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 instructions/mouse-lin/frame-smith/agents-mdgit clone --depth 1 https://github.com/mouse-lin/frame-smithWhat 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.02962 | $0.02962 |
| Opus 5 | $0.01481 | $0.01481 |
| Sonnet 5 | $0.00592 | $0.00592 |
| Haiku 4.5 | $0.00296 | $0.00296 |
Grade A, and why
frame-smith AGENTS.md 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 3d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
frame-smith — Agent Instructions
For OpenAI Codex and other agent runtimes that read
AGENTS.md. The full skill is atskills/frame-smith/SKILL.md. Deep reference material lives inskills/frame-smith/references/. Load what you need per phase — do not inline everything at once.
What frame-smith does
frame-smith is a director, not a renderer. It reads a brief, decides what the video is, writes a Remotion composition (.tsx), and registers it — but it does not own the runtime. It builds two registers:
- cinematic — a landscape clip,
1920×1080 · 30fps, ~12–24s, pure visual, no voiceover (music + SFX still apply), ending on a wordmark/logo payoff. - short — a vertical clip,
1080×1920, for 抖音/小红书/视频号, may carry subtitles + voiceover, hook by ~1.5s. Obeys theS = width/720scale system and 抖音 safe zones.
The through-line both share: high motion craft, zero motion-slop — the motion craft floor and the anti-slop blacklist.
0. ENVIRONMENT GATE — hard requirement, run FIRST
frame-smith cannot render on its own. At least one of the hyperframe or remotion skills (or a Remotion project on disk) must be present — see skills/frame-smith/references/environment.md, or run bash skills/frame-smith/scripts/check-runtime.sh.
- Neither present → STOP. Write no
.tsx. Report it and offer install (hyperframepreferred — carries the effect templates;remotion= leaner runtime). Ask for a path before assuming any; never hardcode one. - One present → record which (it decides where the composition lands + how to register/preview), then proceed.
Commands (targeted iteration)
A full build runs the whole workflow below. For iterating on an existing composition, route the request through one verb instead of rebuilding — Codex has no slash commands, so map the user's intent to the verb and load only that reference. The env gate (§0) still runs first for any verb that writes or renders.
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.
- 3d ago First seen · 139 lines · 2,962 tokens per session scan A 2766b7419992
frame-smith AGENTS.md is an instructions file published in the GitHub repository mouse-lin/frame-smith (52 stars, last pushed 1mo ago), licensed MIT. It adds 2,962 tokens to every session, about $0.0148 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.