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/release-versionnpx skills add OpenVidu/openvidu.io --skill release-versiongit 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/release-version)<a href="https://agentmods.dev/skills/openvidu/openvidu.io/release-version"><img src="https://agentmods.dev/badge/skills/openvidu/openvidu.io/release-version.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.00102 | $0.00970 |
| Opus 5 | $0.00051 | $0.00485 |
| Sonnet 5 | $0.00020 | $0.00194 |
| Haiku 4.5 | $0.00010 | $0.00097 |
Grade A, and why
release-version 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 5d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Releasing a documentation version
The recurring sequence for release-day docs work. The mechanics live in
publish-tool/README.md ("What a publish does"); this skill
is the order of operations and the contracts that make a publish fail.
1. Know which publish this is
| Situation | Command | Effect |
|---|---|---|
New minor release (docs merged from next) |
ovweb publish new X.Y |
Deploys the version, points latest at it, refreshes the root pages, creates the X.Y branch |
| Content fix or patch release of the current minor | ovweb publish latest X.Y |
Rebuilds the newest version from main in place; rebases the X.Y branch |
| Fix to an older minor | ovweb publish past X.Y |
Commit to the X.Y branch first; root pages untouched |
Patch releases do not create a new documentation version: they update the existing X.Y
in place and add their notes under it.
2. Releases pages (docs/meet/releases.md, docs/docs/releases.md)
Strict contract — ovweb fails the publish on violations:
- Each minor gets one top-level
## X.Y.0section. Later patches go under it, as#### X.Y.Zbeneath a### Patch releasesheading — never a new top-level section. - Every link inside a version's notes is absolute, domain-qualified and pinned to that same
version (
https://openvidu.io/X.Y/docs/...) — never relative, neverlatest. The notes are spliced into every version folder on publish, so any other form is wrong for most copies.ovweb lintcatcheslatesthere at PR time. - Prefer additive docs changes: each
X.Yfolder serves only its newest patch, so a page or anchor an older patch's notes link to has nothing to fall back to if removed. When a target must move, fix the affected release-notes links in the same change.
3. Version gates in publish-tool/ovweb.yaml
If pages moved or were removed in this release, add redirect rules gated to the release the
change belongs to (e.g. versions: ">=3.9"), never inferred from what a version folder
currently contains. Run ovweb redirects check. New legacy folders or rule changes for other
versions need ovweb redirects apply on gh-pages after the publish.
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.
- 5d ago First seen · 67 lines · 102 tokens per session scan A 5682fa664fad
release-version is a skill published in the GitHub repository OpenVidu/openvidu.io (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 102 tokens to every session and 970 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…