vidin: Instructions file for Codex

AGENTS.md

vidin AGENTS.md is an instructions file for Codex, OpenCode from teunlao/vidin. It costs 1,075 tokens per session, scanned A, original, MIT.

Project instructions for Vidin, a command-line tool and MCP server that turns screen recordings into a small set of annotated frames an agent can inspect. MCP is a way for tools to provide capabilities to AI agents.

In plain words
What is it for?
Use them when changing Vidin's selector, command-line tool, MCP server, tests, fixtures, or build. They document commands, required tools such as ffmpeg, supported runtimes, and rules about which APIs may be used.
Why use it?
They preserve important design decisions and runtime constraints, such as selecting frames based on events and keeping published code compatible with Node.js.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is teunlao/vidin's own configuration. It tells Codex and OpenCode how to work on vidin itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vidin configures →

Reuse

Borrowing it

Nothing to install: this file belongs to teunlao/vidin. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/teunlao/vidin/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/teunlao/vidin

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for vidin AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/teunlao/vidin/agents-md/github.svg)](https://agentmods.dev/instructions/teunlao/vidin/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/teunlao/vidin/agents-md"><img src="https://agentmods.dev/badge/instructions/teunlao/vidin/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for vidin AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/teunlao/vidin/agents-md"><img src="https://agentmods.dev/badge/instructions/teunlao/vidin/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,075 This file is loaded in full into every session.
When invoked 1,075 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01075 $0.01075
Opus 5.5 $0.00430 $0.00430
Sonnet 5.5 $0.00215 $0.00215
Haiku 4.5 $0.00108 $0.00108

Measured 1mo ago against content hash f762a7b3994f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vidin 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 1mo 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.

AGENTS.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

vidin turns a screen recording into a small set of annotated keyframes an agent can read, exposed as a CLI and an MCP server. The design rationale — why frames are selected on events instead of sliced on an interval — is in README.md; read it before touching the selector.

Commands

bun test              # full suite, ~17s; needs ffmpeg, builds the fixture on first run
bunx tsc --noEmit     # typecheck (development runs .ts directly, no build)
bun run build         # tsc → dist/ — what npm ships; runs on plain Node ≥ 20
bun run vidin <file>  # CLI: analyse a video into ./.vidin/<name>/
bun run mcp           # MCP server on stdio
bun run fixture       # regenerate fixtures/screen-bug.mp4 (synthetic, scripted timeline)

Toolchain: Bun ≥ 1.1 (development only) and ffmpeg/ffprobe on PATH. yt-dlp is needed only for URL input. The published package is @teunlao/vidin (plain vidin is blocked by npm's similarity check against vision); it targets Node ≥ 20 via npx, and end users never need Bun.

Hard rules

  • No Bun APIs in src/ or bin/. The npm package runs under whatever npx resolves to, so runtime code uses node: APIs exclusively. Bun (which implements them) is the dev runner; Bun.* is allowed only in scripts/ and test/.
  • No image libraries. All drawing (change boxes, labels, contact sheets) is ffmpeg filters in src/core/render.ts. Do not add sharp/canvas/jimp — keeping ffmpeg the only native dependency is a design goal, not an accident.
  • Runtime dependencies stay at two: @modelcontextprotocol/sdk and zod. Adding one is a design decision to raise, not a convenience.
  • Imports carry explicit .ts extensions; ESM only. tsconfig.build.json rewrites them to .js when emitting dist/.

Selector invariants (src/core/select.ts)

Breaking either one is a correctness bug, not a tuning choice; test/regressions.test.ts pins them:

  1. The diff baseline advances only by emitting. No code path may fold a changed screen into the reference without keeping a frame — every later diff would then measure zero against a state the reader never sees.
  2. Annotations describe the surviving neighbour. After budget pruning, each frame's deltaPct and regions are recomputed (relink) against the frame that actually precedes it in the final list.

Read the full file on GitHub · 92 lines

Changes

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.

  1. 1mo ago First seen · 92 lines · 1,075 tokens per session scan A f762a7b3994f

Subscribe to this mod's changes

vidin AGENTS.md is an instructions file published in the GitHub repository teunlao/vidin (2 stars, last pushed 8d ago), licensed MIT. It adds 1,075 tokens to every session, about $0.0043 per session on Opus 5.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-31.

Related

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).

microsoft/vscode · 9,649 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,549 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens