Borrowing it
Nothing to install: this file belongs to Cuongyd196/auto-compare-video. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Cuongyd196/auto-compare-video/main/CLAUDE.mdgit clone --depth 1 https://github.com/Cuongyd196/auto-compare-videoWrote 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/cuongyd196/auto-compare-video/claude-md)<a href="https://agentmods.dev/instructions/cuongyd196/auto-compare-video/claude-md"><img src="https://agentmods.dev/badge/instructions/cuongyd196/auto-compare-video/claude-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.1 | $0.01714 | $0.01714 |
| Opus 5 | $0.00857 | $0.00857 |
| Sonnet 5 | $0.00343 | $0.00343 |
| Haiku 4.5 | $0.00171 | $0.00171 |
Grade A, and why
auto-compare-video 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 7d 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.
This is a copy
100% identical to auto-compare-video AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HyperFrames Composition Project
Repo layout — multiple videos
This repo holds a series of short comparison videos, each its own self-contained
HyperFrames project under videos/<video-name>/ (own package.json, hyperframes.json,
meta.json, index.html, assets/, scripts/, renders/, snapshots/). Root-level files
(README.md, CLAUDE.md, AGENTS.md, DESIGN.md, vbee.md) are shared across the whole
series — DESIGN.md in particular is the fixed layout/style contract every video follows.
All commands below run with cwd inside the specific video's folder
(videos/<video-name>/), not the repo root — that's where each video's package.json lives.
The Vbee TTS credentials (.env) live once at the repo root and are shared by every
video's scripts/generate-vo.mjs.
To start a new video: create videos/<new-name>/, run hyperframes init inside it, copy the
3-zone layout contract from DESIGN.md, and swap in the new topic's text/images/audio.
Skills — USE THESE FIRST
Always invoke the relevant skill before writing or modifying compositions. Skills encode framework-specific patterns (e.g., window.__timelines registration, data-* attribute semantics, shader-compatible CSS rules) that are NOT in generic web docs. Skipping them produces broken compositions.
Doing anything with HyperFrames? Start at /hyperframes — it tells you what HyperFrames can do and which skill or workflow handles your intent (make a video, TTS / BGM, prep footage, author / animate, render, install blocks), and routes every "make me a…" request (a video, a deck, a composition port) to the right workflow. Read it first, especially when there's no project context to orient you. The workflows it routes to:
/product-launch-video— a product URL or brief / script → 60-90s product launch / SaaS / promo video./website-to-video— a general website / URL → a video of the site (tour / showcase / social clip from captured visuals); a product launch / promo is/product-launch-video./faceless-explainer— arbitrary text (topic / article / notes), no URL, no website capture → 60-90s faceless explainer./embedded-captions— an existing talking-head video (MP4) → the same footage with captions / subtitles added (rail + embed, or pure-cinematic embed); the footage itself is untouched./talking-head-recut— an existing talking-head / interview / podcast video (MP4) → the same footage packaged with designed graphic overlays (kinetic titles, lower-thirds, data callouts, pull-quotes, side panels, pip) synced to the transcript; the clip plays unchanged underneath. (Plain captions/subtitles →/embedded-captions.)/pr-to-video— a GitHub PR (URL /owner/repo#N/ "this PR") → 30-90s code-change explainer (changelog / feature reveal / fix / refactor)./motion-graphics— a short (typically under 10s) design-led motion graphic, motion-is-the-message, no narration: kinetic type, a stat / number count-up, a chart, a logo sting, a lower-third / overlay, or an animated tweet / headline / captured-page highlight; rendered to MP4 or a transparent overlay. Longer / narrated / custom →/general-video./music-to-video— a music track (audio file, or video to pull audio from) → beat-synced video (lyric / slideshow / kinetic promo). Music drives pacing; user-supplied images / videos are cut onto the same beat grid./slideshow— a presentation / pitch deck / interactive deck — discrete slides, fragment reveals, branching, hotspot navigation, presenter mode. Output is a navigable deck, not a rendered video./general-video— fallback for any other video (title card, longer brand / sizzle reel, multi-scene montage, static loop, custom composition); the original hyperframes authoring flow, any length.
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.
- 7d ago First seen · 110 lines · 1,714 tokens per session scan A 8aecf96f71f8
auto-compare-video CLAUDE.md is an instructions file published in the GitHub repository Cuongyd196/auto-compare-video (167 stars, last pushed 11d ago), licensed MIT. It adds 1,714 tokens to every session, about $0.0086 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to auto-compare-video AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
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.
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).
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.
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).
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.