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/elahlabs/elah/agents-mdgit clone --depth 1 https://github.com/elahlabs/elahWrote 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/elahlabs/elah/agents-md)<a href="https://agentmods.dev/instructions/elahlabs/elah/agents-md"><img src="https://agentmods.dev/badge/instructions/elahlabs/elah/agents-md.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.01568 | $0.01568 |
| Opus 5 | $0.00784 | $0.00784 |
| Sonnet 5 | $0.00314 | $0.00314 |
| Haiku 4.5 | $0.00157 | $0.00157 |
Grade A, and why
elah 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 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Brief for coding agents working inside this repository.
Building an app that consumes Elah, rather than working on Elah itself? Read
docs/ai/ELAH_FOR_AI_AGENTS.mdinstead — it is a single self-contained integration guide and needs no repo checkout.
What this is
Elah is a browser-native, frame-accurate video editing engine. A framework-agnostic core (timeline engine, pure resolver, WebGL2 renderer, WebCodecs decode, MP4 export) with React bindings layered on top, plus a headless CLI that renders the same projects server-side.
Three invariants hold everywhere. Do not violate them:
- Time is integer frames. Never store or compute positions in float seconds. Convert at
the edges with
secondsToFrames/framesToSeconds. - One mutation funnel. Every project edit goes through
TimelineEngine. The Zustand stores are read-only mirrors — writing to them desyncs the UI and breaks undo. - The resolver is pure.
resolveTimeline(frame, project) → Scenehas no side effects and no I/O. Renderers consumeSceneand nothing else; they never read the engine or the project directly.
Layout
| Path | What lives there |
|---|---|
packages/core |
Engine, resolver, WebGL2 renderer, demux/decode, stores, export. Zero React — enforced by src/no-react-imports.test.ts. |
packages/react |
React bindings only: editor context, store hooks, audio hooks. |
packages/timeline |
The <Timeline> UI — tracks, clips, ruler, playhead, drag/trim/snap. |
packages/editor |
Batteries-included composition: EditorProvider, Preview, panels. Re-exports the public API of the three above. |
packages/cli |
elah build / export / serve — headless rendering via Playwright + system Chrome. Versioned independently. |
apps/web |
The marketing + docs site (elah.dev). Docs pages are hand-written TSX, not MDX. |
apps/server |
Render-server example built on @elah/cli. |
examples/ |
Standalone example apps that install from npm. Outside the root workspace on purpose — see examples/AGENTS.md. |
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 · 119 lines · 1,568 tokens per session scan A edaaf6895227
elah AGENTS.md is an instructions file published in the GitHub repository elahlabs/elah (40 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,568 tokens to every session, about $0.0078 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.