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/openvidu/openvidu.io/claude-mdgit clone --depth 1 https://github.com/OpenVidu/openvidu.ioWrote 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/openvidu/openvidu.io/claude-md)<a href="https://agentmods.dev/instructions/openvidu/openvidu.io/claude-md"><img src="https://agentmods.dev/badge/instructions/openvidu/openvidu.io/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.01577 | $0.01577 |
| Opus 5 | $0.00788 | $0.00788 |
| Sonnet 5 | $0.00315 | $0.00315 |
| Haiku 4.5 | $0.00158 | $0.00158 |
Grade A, and why
openvidu.io 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 today.
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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Source of https://openvidu.io — MkDocs Material (pinned 9.7.7) + mike, published to gh-pages.
Two versioned products: OpenVidu Meet (docs/meet/, served at /{version}/meet/) and
OpenVidu Platform (docs/docs/, served at /{version}/docs/), plus non-versioned root pages
(landing, pricing, support, blog, …). Merging to main publishes nothing — the live site only
changes when the manual Publish Web workflow runs.
Authoritative references — read the relevant one before working:
contributing/— the canonical contributor docs:authoring.md(pages, snippets, assets),link-rules.md,page-composition.md(page features, overrides, HTML, light/dark),versioning.md(branches, releases pages, publishing),local-testing.md,checks.md(lint, CI).publish-tool/README.md— theovwebCLI and what a publish does; design internals inpublish-tool/docs/.shared/README.md— snippet folder layout.README.md— the repo index (repository map + full documentation index).- Skills: blog work →
blog-plan/blog-write/blog-review(conventions in.claude/skills/blog-write/references/conventions.md); page edits →edit-website; release-day publishing →release-version; demo videos →video-recording. Commands:/check-web,/publish-post,/serve. Agents: PR review →pr-reviewer. APostToolUsehook auto-lints every edit todocs/,shared/or the overrides — fix what it reports.
Branches
next— docs for the version in development (merged tomainon release).main— fixes to published content and non-versioned pages.X.Y— past versions; fixes to an old minor are committed there, never tomain.
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.
- today Changed 8c4d254e7347
- yesterday Changed · +4 lines · +76 tokens per session 6790ad20bc2c
- 5d ago First seen · 96 lines · 1,501 tokens per session scan A 954680631c44
openvidu.io CLAUDE.md is an instructions file published in the GitHub repository OpenVidu/openvidu.io (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,577 tokens to every session, about $0.0079 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.
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.
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.
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).
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.