Borrowing it
Nothing to install: this file belongs to Undertone0809/rudder. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Undertone0809/rudder/main/.agents/skills/maintainer/release-maintainer/SKILL.mdgit clone --depth 1 https://github.com/Undertone0809/rudderWrote 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/undertone0809/rudder/release-maintainer)<a href="https://agentmods.dev/skills/undertone0809/rudder/release-maintainer"><img src="https://agentmods.dev/badge/skills/undertone0809/rudder/release-maintainer/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/undertone0809/rudder/release-maintainer"><img src="https://agentmods.dev/badge/skills/undertone0809/rudder/release-maintainer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00085 | $0.01738 |
| Opus 5.5 | $0.00034 | $0.00695 |
| Sonnet 5.5 | $0.00017 | $0.00348 |
| Haiku 4.5 | $0.00009 | $0.00174 |
Grade A, and why
release-maintainer 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Maintainer
Ship or inspect Rudder releases without losing source identity, authorization, or public-surface completeness.
Route Before Reading
Read references/shared.md, then exactly one primary branch:
references/stable.md: stable readiness, publish, public notes, Desktop update drill, post-stable cleanup, next-version handoff, and the gate before public announcement.references/canary.md: automatic canary publication, first npm bootstrap, Desktop prerelease assets, and temporary pre-stablelatestbehavior.references/rollback.md: move npm dist-tags to an already published version without unpublishing packages or rewriting tags.references/partial-recovery.md: npm/tag/Release/Desktop/docs surfaces disagree, a workflow failed after partial publication, or install lookup returns misleading errors.references/setup.md: one-time GitHub environment, npm trusted-publishing, and workflow setup.references/announcement.md: manual Rudder Discord announcement after a stable release has converged. This is a stable closeout add-on, not a primary release branch.
Use a second branch only when the observed state genuinely crosses branches, such as a stable publish that needs partial recovery. Do not preload every reference for a readiness question.
For a requested Rudder stable release, read references/announcement.md after
the release surfaces are verified. Zeeland explicitly authorized this default
on 2026-09-08: send one release announcement to Rudder / #announcements unless
the user opts out. Reuse that standing authority without a second confirmation.
Read-only checks, canaries, and publishing only a named non-release surface do
not trigger it. Do not add announcements to Release CI or create a webhook.
Authorization Boundary
An explicit request to release a Rudder version, such as release vX.Y.Z,
ship this version, or 发版 in a version-release context, authorizes the
complete standard release lifecycle below. A request to publish only named docs,
a package, or another surface authorizes that surface and its prerequisites.
Resolve a bare publish from context; do not expand it into a full version release.
What ships with it
9 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.
- today Changed 106e69220f92
- 1mo ago Changed · +1 lines 98f31b0efd77
- 1mo ago Changed · +4 lines 3fc4c2954921
- 1mo ago Changed · +6 lines b487a4fdc529
- 1mo ago Changed · +17 lines · +3 tokens per session d14dcf2d37b0
- 2mo ago First seen · 133 lines · 82 tokens per session scan A bd76d88e9f04
release-maintainer is a skill published in the GitHub repository Undertone0809/rudder (294 stars, last pushed yesterday), licensed Apache-2.0. It adds 85 tokens to every session and 1,738 once invoked, about $0.0003 per session on Opus 5.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-30.
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.
release
Fully automate a release with version-bump and childhood.
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.