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/tstambulsky/auto-vlog-editor/agents-mdgit clone --depth 1 https://github.com/tstambulsky/auto-vlog-editorWrote 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/tstambulsky/auto-vlog-editor/agents-md)<a href="https://agentmods.dev/instructions/tstambulsky/auto-vlog-editor/agents-md"><img src="https://agentmods.dev/badge/instructions/tstambulsky/auto-vlog-editor/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.1 | $0.01686 | $0.01686 |
| Opus 5 | $0.00843 | $0.00843 |
| Sonnet 5 | $0.00337 | $0.00337 |
| Haiku 4.5 | $0.00169 | $0.00169 |
Grade A, and why
auto-vlog-editor 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 6d 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 — working in this codebase
Operational rules and non-obvious gotchas for anyone (human or AI agent) editing
this repo. Architecture and feature explanations live in docs/.
Rule of thumb: info needed to NOT break things → here. Info to understand how it works →
docs/.
Knowledge map
| Topic | Doc |
|---|---|
| Catalog / index | docs/index.md |
| Pipeline & beat-sync architecture | docs/architecture/pipeline.md |
| Rendering (ffmpeg, HDR, audio, subtitles) | docs/architecture/rendering.md |
| Publishing API (Zernio) | docs/integrations/zernio.md |
| Voiceover (ElevenLabs) | docs/integrations/elevenlabs.md |
| Telegram bot UX & approval flow | docs/integrations/telegram.md |
| Deployment | docs/operations/deploy.md |
| Web dashboard (read-only) | docs/operations/dashboard.md |
| Design decisions | docs/product/decisions.md |
Hard rules
- Never publish without approval. Only a day in the
approvedstate can create posts; the single gate ispublishing.publish_day(). Don't add publish paths anywhere else. - Never call the Claude CLI outside
app/claude_cli.py. It's the swappable reasoning layer (CLAUDE_CODE_COMMAND): serialized, schema-validated, read-only tools. Everything that needs the model goes throughrun_structured. - Secrets never go into prompts or git. Real keys live only in
.env(which is gitignored)..env.exampledocuments the variables with placeholders.
Critical gotchas
Subtitles/beats: ASR gives TIMING, the script gives TEXT
Word timings (words_v{N}_{lang}.json, which drive BOTH subtitles and beats) come
from app/services/align.py: faster-whisper transcribes the mp3, wav2vec2 refines
per-word timing. The transcription's TEXT is often mis-heard, so retext_to_script
re-maps the timed words onto the KNOWN script (difflib) and emits the script tokens
verbatim — the subtitle word TEXT is ALWAYS the script, never the ASR. This runs
on every path, including fallbacks (WhisperX align → free-form faster-whisper →
char alignment). Don't remove the re-text step or let any path set word text from
ASR. torch is CPU-only and lives in the Dockerfile prod stage (the dev image has
none → exercises the fallback). See docs/architecture/rendering.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.
- 6d ago First seen · 119 lines · 1,686 tokens per session scan A 9508e4fb69d9
auto-vlog-editor AGENTS.md is an instructions file published in the GitHub repository tstambulsky/auto-vlog-editor (11 stars, last pushed 2mo ago), licensed MIT. It adds 1,686 tokens to every session, about $0.0084 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).
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 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.
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.