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/jacobcwright/open-animate/claude-mdgit clone --depth 1 https://github.com/jacobcwright/open-animateWhat 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.01598 | $0.01598 |
| Opus 5 | $0.00799 | $0.00799 |
| Sonnet 5 | $0.00320 | $0.00320 |
| Haiku 4.5 | $0.00160 | $0.00160 |
Grade A, and why
open-animate CLAUDE.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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — oanim (open-animate)
Rules
-
Use subagents for research. When looking up Remotion APIs, fal.ai docs, or any external reference, spawn a subagent (Explore or general-purpose) instead of doing inline research. Keep the main context focused on implementation.
-
Update progress.md and prd.json after each task. When completing work:
- Append a dated entry to
progress.mddescribing what was done - Update the relevant ticket(s) in
prd.json— setstatusto"done", add notes if needed - Add new tickets to
prd.jsonfor any follow-up work discovered
- Append a dated entry to
-
Build before committing. Always run
pnpm buildand verify it succeeds before committing. The core package must produce valid DTS output (no TypeScript errors in declaration generation). -
Remotion type constraints.
TransitionPresentation<T>requiresT extends Record<string, unknown>. Any props interfaces for transitions must useextends Record<string, unknown>. This was a real build failure — don't repeat it. -
Test against real Remotion. When adding or modifying @oanim/core components, verify they work in at least one example project (
examples/hello-worldorexamples/launch-video) by checkingnpx remotion studioopens. -
Keep the CLI thin. The
oanimCLI wraps Remotion's own tooling — it does not reimplement rendering.oanim rendershells tonpx remotion renderwith config fromanimate.json. -
No JSX in .ts files. Remotion components use React.createElement() in
.tsfiles or JSX in.tsxfiles. The core package usesReact.createElement()throughout for maximum compatibility. Keep this consistent. -
Workspace topology matters. Both
packages/*andexamples/*are in the pnpm workspace. Examples reference@oanim/coreasworkspace:*. This meanspnpm installat root links them automatically.
What is oanim
Open-source CLI + component library + agent skill for creating React motion graphics via Remotion and exporting MP4.
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 · 140 lines · 1,598 tokens per session scan A 5ca0a86b5964
open-animate CLAUDE.md is an instructions file published in the GitHub repository jacobcwright/open-animate (23 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 1,598 tokens to every session, about $0.0080 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.