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 buYoung/skills --skill release-itgit clone --depth 1 https://github.com/buYoung/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/buyoung/skills/release-it)<a href="https://agentmods.dev/skills/buyoung/skills/release-it"><img src="https://agentmods.dev/badge/skills/buyoung/skills/release-it/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/buyoung/skills/release-it"><img src="https://agentmods.dev/badge/skills/buyoung/skills/release-it.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 26 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 29 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00080 | $0.01837 |
| Opus 5 | $0.00040 | $0.00919 |
| Sonnet 5 | $0.00016 | $0.00367 |
| Haiku 4.5 | $0.00008 | $0.00184 |
Grade A, and why
release-it 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
release-it Release Automation
release-it is a generic, pluggable CLI tool that automates versioning and package publishing. It handles version bumping, Git committing/tagging/pushing, npm publishing, and GitHub/GitLab release creation -- all in a single configurable workflow. Language-agnostic with a powerful plugin system for extending behavior.
Default Interactive Contract
Generate pnpm release using the project entry script and @inquirer/prompts adapter in
interactive-workflow.md. All release questions use
Inquirer; release-it performs the version update and Git operations.
- Single project:
pnpm release → choose version → confirm commit / commit → confirm tag / tag → confirm push / push. - Monorepo:
pnpm release → choose one service app → choose version → confirm commit / commit → confirm tag / tag → confirm push / push.
The first question in a non-monorepo is the version selection. Do not add an app picker or a separate start confirmation. In a monorepo, offer only the verified service apps with a single-select picker, even when there is only one eligible app. Resolve an unclear service app boundary during setup, then use that app's version source, changelog, and tag policy.
Display the current version and concrete next versions. Always wait for the user's selection; recommended increments, existing settings, and CI environment variables cannot replace it. Pass the selected exact version and target configuration to release-it's API.
Ask each Git confirmation at its release-it execution point and await that action before
asking the next. A negative answer or cancellation stops that action and the entire remaining
flow. Use Inquirer's native y/n confirmation with default: false, so Enter declines;
Ctrl+C cancels the active question. Report the actual remaining files, index, commit, tag,
and push status; do not promise automatic rollback. Check for an interactive terminal before any release work. Do not use
--ci, --only-version, canned answers, or a direct push hook in this default path.
What ships with it
19 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.
- evals/comparison-results.md 2.7 KB
- evals/evals.json 11 KB
- evals/interactive-results.json 10 KB
- evals/README.md 4.4 KB
- evals/run_interactive.py 19 KB runs code
- examples/interactive-release/release-prompts.mjs 2.3 KB runs code
- examples/interactive-release/release.mjs 7.2 KB runs code
- references/cli-and-workflow.md 8.9 KB
- references/configuration.md 9.0 KB
- references/custom-plugin-development.md 10 KB
- references/git-integration.md 7.0 KB
- references/github-gitlab-releases.md 5.3 KB
- references/hooks-and-lifecycle.md 5.0 KB
- references/initial-setup.md 10 KB
- references/interactive-workflow.md 12 KB
- references/monorepo.md 4.7 KB
- references/npm-publishing.md 5.3 KB
- references/plugins.md 6.4 KB
- references/troubleshooting.md 8.0 KB
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 · +26 lines · +10 tokens per session 60dd6c942054
- 9d ago First seen · 96 lines · 70 tokens per session scan A 4e4eb98f24f8
release-it is a skill published in the GitHub repository buYoung/skills (21 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 1,837 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
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.
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.
updater_guide
Guidance for checking for and installing Row-Bot updates.