A release workflow for publishing a new version of an npm package, a reusable JavaScript or TypeScript library. It checks the project, updates the version, pushes a commit, and creates a GitHub Release.

Use it to publish patch, minor, or major package updates. It helps check the branch and project status, run tests and builds, update package.json, and create a GitHub Release.

It reduces the chance of publishing with uncommitted changes or failing tests. It also keeps version changes, Git tags, and release notes together.

How weselow/Yandex-webmaster-mcp-server configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to weselow/Yandex-webmaster-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/weselow/Yandex-webmaster-mcp-server/master/.claude/skills/release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/weselow/Yandex-webmaster-mcp-server

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/weselow/yandex-webmaster-mcp-server/release/github.svg)](https://agentmods.dev/skills/weselow/yandex-webmaster-mcp-server/release)

Your own site

<a href="https://agentmods.dev/skills/weselow/yandex-webmaster-mcp-server/release"><img src="https://agentmods.dev/badge/skills/weselow/yandex-webmaster-mcp-server/release/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/weselow/yandex-webmaster-mcp-server/release"><img src="https://agentmods.dev/badge/skills/weselow/yandex-webmaster-mcp-server/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 676 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00045	$0.00676
Opus 5	$0.00023	$0.00338
Sonnet 5	$0.00009	$0.00135
Haiku 4.5	$0.00005	$0.00068

Measured 9d ago against content hash 6d8d52bbaa36, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

release 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 9d 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.

.claude/skills/release/SKILL.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Публикация релиза

Пошаговый процесс

Шаг 1: Проверка готовности

Перед релизом убедись, что:

Все изменения закоммичены:
```
git status
```
Тесты проходят:
```
pnpm build && pnpm test
```
Ты на ветке main/master

Если есть незакоммиченные изменения или тесты не проходят — останови процесс и сообщи пользователю.

Шаг 2: Определи тип версии

Спроси пользователя через AskUserQuestion, какой тип версии:

patch (1.0.0 → 1.0.1) — баг-фиксы, мелкие исправления
minor (1.0.0 → 1.1.0) — новые функции, обратно совместимые
major (1.0.0 → 2.0.0) — ломающие изменения

Покажи текущую версию из package.json и какой станет новая.

Шаг 3: Обнови версию

npm version <patch|minor|major> --no-git-tag-version

Это обновит version в package.json без создания git-тега (тег создаст GitHub Release).

Шаг 4: Закоммить и запуш

git add package.json
git commit -m "chore: bump version to <NEW_VERSION>"
git push origin main

Шаг 5: Создай GitHub Release

gh release create v<NEW_VERSION> --title "v<NEW_VERSION>" --generate-notes

Флаг --generate-notes автоматически создаст описание из коммитов.

Шаг 6: Подтверди публикацию

Сообщи пользователю:

Новая версия: v<NEW_VERSION>
GitHub Release создан
GitHub Actions запустит публикацию в npm автоматически
Проверить статус: gh run list --limit 1

Первоначальная настройка npm (одноразово)

Если пакет ещё не был опубликован, пользователю нужно:

Создать аккаунт на npmjs.com
Сгенерировать Access Token: npmjs.com → Avatar → Access Tokens → Generate New Token → тип Automation
Добавить секрет в GitHub: repo → Settings → Secrets and variables → Actions → New repository secret → имя NPM_TOKEN, значение — токен
Первый релиз: gh release create v1.0.0 --title "v1.0.0" --notes "Первый релиз"

Проверка публикации

# Статус workflow
gh run list --limit 1

# Проверить пакет в npm
npm view yandex-webmaster-mcp-server version

Read the full file on GitHub · 86 lines

Changes

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.

9d ago First seen · 86 lines · 45 tokens per session scan A 6d8d52bbaa36

Subscribe to this mod's changes

release is a skill published in the GitHub repository weselow/Yandex-webmaster-mcp-server (5 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 676 once invoked, about $0.0002 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.

Git and workflow Releases

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.

paperclipai/paperclip · 42 tokens

multi-agent-release-manager

Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.

chromium/chromium · 27 tokens

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.

phuryn/pm-skills · 57 tokens

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.

aeonfun/aeon · 27 tokens

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.

NVIDIA/nvcf · 61 tokens

updater_guide

Guidance for checking for and installing Row-Bot updates.

siddsachar/row-bot · 17 tokens

Yandex-webmaster-mcp-server: Skill for Claude Code