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 skills/openvidu/openvidu.io/edit-websitenpx skills add OpenVidu/openvidu.io --skill edit-websitegit 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/skills/openvidu/openvidu.io/edit-website)<a href="https://agentmods.dev/skills/openvidu/openvidu.io/edit-website"><img src="https://agentmods.dev/badge/skills/openvidu/openvidu.io/edit-website.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.00090 | $0.00967 |
| Opus 5 | $0.00045 | $0.00483 |
| Sonnet 5 | $0.00018 | $0.00193 |
| Haiku 4.5 | $0.00009 | $0.00097 |
Grade A, and why
edit-website 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenVidu Website Editor
This repo is the source of https://openvidu.io/ (MkDocs Material → gh-pages; content under
docs/). CLAUDE.md carries the always-on invariants; this skill is the workflow. The
knowledge lives in contributing/ — read the file that matches the
task before editing.
Branch to work on
next for the version in development, main for fixes to published content, X.Y for past
versions — details in contributing/versioning.md.
Read the doc that matches the task
| Task touches… | Read first |
|---|---|
| Any internal link or image reference | contributing/link-rules.md |
| A new page, snippet or asset (placement, frontmatter, nav, llmstxt, layout) | contributing/authoring.md + shared/README.md |
HTML blocks, page_features:, theme overrides/partials, JSON-LD frontmatter, light/dark images |
contributing/page-composition.md |
| URLs, versions, redirects, the releases pages | contributing/versioning.md (+ publish-tool/README.md) |
| Blog posts | The blog-plan/blog-write/blog-review skills, not this one |
The facts that bite most often
- Copy a visual pattern → copy its
page_features:too — the feature keys load the JS/CSS the pattern needs. - GLightbox HTML: the
#only-dark/#only-lightsuffix goes in the<img>/<video>src, never in the parent<a href>, and each<a>must be a one-liner. shared/snippets render on many pages — grep the snippet's--8<--usages before editing one.- Touched a tutorial page? Flag the livekit-tutorials-docs sync to the user (procedure at
the end of
contributing/authoring.md).
Local testing
/serve starts the dev server; /check-web validates like CI. Expected local behaviors
(unversioned root, local canonicals) and the versioned-layout preview are in
contributing/local-testing.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 · 65 lines · 90 tokens per session scan A 85c54c89c212
edit-website is a skill published in the GitHub repository OpenVidu/openvidu.io (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 90 tokens to every session and 967 once invoked, about $0.0005 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…