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/undertone0809/rudder/release-maintainernpx skills add Undertone0809/rudder --skill release-maintainergit 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.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.00085 | $0.01549 |
| Opus 5 | $0.00043 | $0.00775 |
| Sonnet 5 | $0.00017 | $0.00310 |
| Haiku 4.5 | $0.00009 | $0.00155 |
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 yesterday.
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 — 150 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 every hands-on stable release, also read references/announcement.md after
the public surfaces, cleanup, and next-version handoff are verified. Keep this
as an authenticated maintainer action; do not add it to Release CI or create a
webhook unless the user explicitly asks for announcement automation.
Authorization Boundary
An explicit imperative such as release, publish, ship this version,
发版, or 发布 authorizes the complete standard release lifecycle:
- resolve and lock the single consistent version and source SHA;
- land reviewed release source on
mainwhen needed; - run required exact-source CI, preflight, and package validation once;
- publish npm, tag, GitHub Release, Desktop, and production-docs surfaces;
- verify public installation, clean obsolete canary Releases/tags, and advance the next-version base;
- publish and read back the stable release announcement in Rudder Discord.
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.
- yesterday Changed · +17 lines · +3 tokens per session d14dcf2d37b0
- 6d ago First seen · 133 lines · 82 tokens per session scan A bd76d88e9f04
release-maintainer is a skill published in the GitHub repository Undertone0809/rudder (288 stars, last pushed yesterday), licensed Apache-2.0. It adds 85 tokens to every session and 1,549 once invoked, about $0.0004 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-30.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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
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…