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/copilot-instructionsgit clone --depth 1 https://github.com/mouse-lin/frame-smithWrote 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/instructions/mouse-lin/frame-smith/copilot-instructions)<a href="https://agentmods.dev/instructions/mouse-lin/frame-smith/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/mouse-lin/frame-smith/copilot-instructions.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.01382 | $0.01382 |
| Opus 5 | $0.00691 | $0.00691 |
| Sonnet 5 | $0.00276 | $0.00276 |
| Haiku 4.5 | $0.00138 | $0.00138 |
Grade A, and why
frame-smith copilot-instructions.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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions: frame-smith Motion Standard
GitHub Copilot reads this file automatically. These rules replace generic AI motion defaults with frame-smith's never-cheap, effect-engine-driven standards for Remotion video compositions.
Core Directive
You are generating a Remotion video composition for a frame-smith project. frame-smith is a director, not a renderer — it decides what the video is and writes the .tsx; a video runtime renders it. It builds two registers:
- cinematic (landscape
1920×1080, no voiceover, wordmark payoff) — spectacle + one effect engine + a tight beat arc. - short (vertical
1080×1920, 抖音/小红书, may carry subtitles/voiceover) — hook by ~1.5s, readable inside safe zones, cut to narration.
Both are never cheap: the motion craft floor and anti-slop rules apply to both.
0. Environment gate — before writing any composition
A composition needs a runtime. Confirm the hyperframe or remotion skill (or a Remotion project on disk) is present before writing .tsx. If neither is, stop and guide install — don't produce a file the user can't run, and never hardcode a project path (ask, or resolve from the working tree).
The 9 Non-Negotiables
-
Read the brief first. Before any code, output a Frame Read:
register={cinematic|short} · engine={the one effect engine} · duration={n}s · ENERGY/SPECTACLE/DENSITY. Name the lazy motion cliché (logo fade + three cards sliding up + soft riser) and state how you're beating it. Then stop for confirmation. -
Time in seconds, always clamped.
const FPS = 30; const f = (s) => Math.round(s*FPS);— every beat/delay isf(seconds), never a raw frame. Everyinterpolateover a time range takesclampOpts(extrapolateLeft/Right: 'clamp'). -
Animate
transform/opacityonly. Nevertop/left/width/height— that's the jank source. Usetranslate/scale/rotate. -
Easing over
linear. EntrancesEasing.out(cubic/exp); popsEasing.out(back())orspring; holds are flat segments in a piecewiseinterpolate.linearon a visible move is a tell.
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 · 59 lines · 1,382 tokens per session scan A d8c94f13bf54
frame-smith copilot-instructions.md is an instructions file published in the GitHub repository mouse-lin/frame-smith (52 stars, last pushed 1mo ago), licensed MIT. It adds 1,382 tokens to every session, about $0.0069 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.