open-video-guide: Instructions file for Codex

AGENTS.md

open-video-guide AGENTS.md is an instructions file for Codex, OpenCode from songod0906/open-video-guide. It costs 406 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for the open-video-guide project. They define writing rules, product claims, project scope, and checks to run before a commit.

In plain words
What is it for?
Use them when editing the repository, writing documentation, describing integrations, or preparing changes for commit.
Why use it?
They keep contributions consistent and help prevent unsupported claims, unclear terminology, and avoidable quality problems.

Instructions file for CodexOpenCode

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

This is songod0906/open-video-guide's own configuration. It tells Codex and OpenCode how to work on open-video-guide 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 open-video-guide configures →

Reuse

Borrowing it

Nothing to install: this file belongs to songod0906/open-video-guide. 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/songod0906/open-video-guide/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/songod0906/open-video-guide

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 open-video-guide AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/songod0906/open-video-guide/agents-md.svg)](https://agentmods.dev/instructions/songod0906/open-video-guide/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/songod0906/open-video-guide/agents-md"><img src="https://agentmods.dev/badge/instructions/songod0906/open-video-guide/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 406 This file is loaded in full into every session.
When invoked 406 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.00406 $0.00406
Opus 5 $0.00203 $0.00203
Sonnet 5 $0.00081 $0.00081
Haiku 4.5 $0.00041 $0.00041

Measured 6d ago against content hash f633cbe4970b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

open-video-guide 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.

AGENTS.md · 69 lines

What it actually says

Repository Instructions

These instructions apply to all files in this repository.

Language

Write technical text in ASD-STE100 Simplified Technical English, Issue 9. Use the project terms in docs/TERMINOLOGY.md.

Use active voice. Use one term for one meaning. Use a maximum of 20 words in a procedural sentence. Use a maximum of 25 words in a descriptive sentence. Put only one instruction in each procedural sentence. Do not use a technical abbreviation before you define it.

Do not change legal license text or exact source text. Do not claim full compliance from an automated language check.

Product truth

Describe the product as local-first and open source. Do not describe the product as a free hosted service. Do not claim that the video pipeline works before tests prove the claim. Do not claim support for a platform before an integration test passes.

Scope

Keep the core engine independent from user interfaces and AI clients. Put platform code in an adapter. Keep model weights, input videos, screenshots, logs, and generated guides out of Git.

Quality

Run these checks before a commit:

python scripts/check_ste.py
python -m pytest
python -m ruff check .

Add an architecture decision record for a change to a major technical decision. Add test evidence for each product capability. Update the risk register when a change adds a material risk.

Shared project handoff

Run this command at the start of each work session:

python scripts/project_context.py

Read .project-context/PROJECT_CONTEXT.md before you plan work. Use docs/PROJECT_STATE.json as the semantic project record.

Update docs/PROJECT_STATE.json when capability, priority, status, or limits change. Do not store conversation transcripts in the project state.

Run this command before a handoff:

make handoff

Give the next agent the repository path. The next agent must refresh the project context before work.

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. 6d ago First seen · 69 lines · 406 tokens per session scan A f633cbe4970b

Subscribe to this mod's changes

open-video-guide AGENTS.md is an instructions file published in the GitHub repository songod0906/open-video-guide (0 stars, last pushed 16d ago), licensed Apache-2.0. It adds 406 tokens to every session, about $0.0020 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-31.

Related

Other instructions, from other repositories

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,296 tokens

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.

openai/codex · 5,182 tokens

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 · 6,785 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 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,469 tokens

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.

github/spec-kit · 7,104 tokens