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 skills add vosslab/vosslab-skills --skill news-release-docsgit clone --depth 1 https://github.com/vosslab/vosslab-skillsWrote 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/vosslab/vosslab-skills/news-release-docs)<a href="https://agentmods.dev/skills/vosslab/vosslab-skills/news-release-docs"><img src="https://agentmods.dev/badge/skills/vosslab/vosslab-skills/news-release-docs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vosslab/vosslab-skills/news-release-docs"><img src="https://agentmods.dev/badge/skills/vosslab/vosslab-skills/news-release-docs.svg" alt="Reviewed on agentmods" width="80" 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.00061 | $0.01165 |
| Opus 5 | $0.00030 | $0.00583 |
| Sonnet 5 | $0.00012 | $0.00233 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
news-release-docs 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 10d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
News and release docs
Overview
Read the verbose docs/CHANGELOG.md (and rotated archives) and author two
differentiated release docs from it:
docs/RELEASE_HISTORY.md: the full, organized, reverse-chronological version log with notable fixes and compatibility detail.docs/NEWS.md: short curated highlights and announcements, not a full changelog.
Both are written in place. The skill also emits a notes-file body to a scratch
path under /tmp for use with devel/make_release.py --notes-file, and reports
that path. The two docs must stay distinct (full log vs curated highlights);
never produce identical content. Base every entry on changelog evidence and
never invent shipped work.
Version source
Determine the target version deterministically:
- If
docs/CHANGELOG.mdcarries explicit version headings, derive the version from the changelog. - When the changelog carries only date blocks (the repo's day-block format),
read the repo-root
VERSIONfile as the version source. - Cross-check
VERSIONagainstpyproject.toml[project] version. If they disagree, report the mismatch and stop; do not guess. See the versioning rules indocs/REPO_STYLE.md(CalVer0Y.0M.PATCH,VERSIONpluspyproject.tomlas the version source).
Use the heading shape ## v<version> - YYYY-MM-DD for every release block. This
matches devel/make_release.py _prepend_release_doc, which inserts a block of
exactly that shape above the first existing ## heading, so the skill output
and the release tool stay compatible.
Workflow
- Gather changelog evidence
- Read the active
docs/CHANGELOG.md. - Read rotated archives
docs/CHANGELOG-YYYY-MM*.mdas needed to cover the release range. See the changelog-rotation rules indocs/REPO_STYLE.md(two newest day blocks stay active; older blocks live in archives). - Collect the day-block subsections (Additions and New Features, Behavior or Interface Changes, Fixes and Maintenance, Removals and Deprecations, Decisions and Failures, Developer Tests and Notes) for the target version.
- Read the active
- Resolve the target version
- Follow the "Version source" steps above.
- Author two differentiated bodies
- Write the
docs/RELEASE_HISTORY.mdblock from references/release_history_template.md: Highlights, Notable fixes, Compatibility notes, Validation. Fuller detail, including secondary items. - Write the
docs/NEWS.mdblock from references/news_template.md: curated Highlights and, only when a real upgrade step exists, Upgrade notes. Terse, headline items only. - Omit any subsection that has no real content. Keep the two bodies clearly different in scope and length.
- Write the
- Prepend in place
- Prepend the
## v<version> - YYYY-MM-DDblock immediately above the first existing##heading in each doc, preserving all older content byte-for-byte. If a## v<version>heading already exists in a doc, report it and stop rather than duplicating.
- Prepend the
- Emit the notes-file body
- Write a notes-file body to a scratch path under
/tmp(for example/tmp/news_release_notes.md) for use asdevel/make_release.py --notes-file, and report that path. The notes-file stays out of the repo; never write a repo-tracked scratch file.
- Write a notes-file body to a scratch path under
- Apply style
- Follow
docs/MARKDOWN_STYLE.md: ASCII only (escape UTF-8 symbols), sentence-case ATX headings,-bullets, relative links with path link text.
- Follow
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 103 lines · 61 tokens per session scan A 95cd3518d98d
news-release-docs is a skill published in the GitHub repository vosslab/vosslab-skills (2 stars, last pushed 14d ago), licensed MIT. It adds 61 tokens to every session and 1,165 once invoked, about $0.0003 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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.