yandex-wiki-search-mcp: Command for Claude Code

.claude/commands/release.md

release is a command for Claude Code from dlbolshov/yandex-wiki-search-mcp. It costs 11 tokens per session (550 once invoked), scanned A, original, Apache-2.0.

A release-preparation command for the Yandex Wiki MCP project, a tool that connects agents to Yandex Wiki search and related functions.

In plain words
What is it for?
Preparing a new project release and keeping package, manifest, server, image, lockfile, and changelog versions consistent.
Why use it?
It coordinates version updates, documentation checks, dependency locking, changelog entries, tests, and the release commit.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md.

This is dlbolshov/yandex-wiki-search-mcp's own configuration. It tells Claude Code how to work on yandex-wiki-search-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything yandex-wiki-search-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to dlbolshov/yandex-wiki-search-mcp. 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/dlbolshov/yandex-wiki-search-mcp/main/.claude/commands/release.md
Clone the repo
git clone --depth 1 https://github.com/dlbolshov/yandex-wiki-search-mcp

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.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/commands/dlbolshov/yandex-wiki-search-mcp/release/github.svg)](https://agentmods.dev/commands/dlbolshov/yandex-wiki-search-mcp/release)
Your own site
<a href="https://agentmods.dev/commands/dlbolshov/yandex-wiki-search-mcp/release"><img src="https://agentmods.dev/badge/commands/dlbolshov/yandex-wiki-search-mcp/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.

agentmods 80×15 button for release

Your own site · 80×15
<a href="https://agentmods.dev/commands/dlbolshov/yandex-wiki-search-mcp/release"><img src="https://agentmods.dev/badge/commands/dlbolshov/yandex-wiki-search-mcp/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 550 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00011 $0.00550
Opus 5.5 $0.00004 $0.00220
Sonnet 5.5 $0.00002 $0.00110
Haiku 4.5 $0.00001 $0.00055

Measured 25d ago against content hash 6c2267da9bac, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 25d 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/commands/release.md · 47 lines

What it actually says

Context

  • Current git status: !git status
  • Current git diff (staged and unstaged changes): !git diff HEAD
  • Current branch: !git branch --show-current
  • Recent commits: !git log --oneline -10
  • Linters status: !task

Task

Prepare a new release of yandex-wiki-search-mcp.

Instructions

  1. Make sure current code passes task.

  2. Verify @README.md, @README_ru.md, and @CLAUDE.md match the current Wiki project, toolset, and configuration.

  3. Decide the next version in @pyproject.toml. Since 1.0.0 the tool surface is the compatibility promise (docs/architecture.md → "Release process"):

    • fixes and documentation-only changes bump patch, including a security fix that closes a hole by taking something away (1.5.2)
    • a new tool, argument or setting, or a deprecated one, bumps minor (1.6.0)
    • a breaking change to the tool surface bumps major

    When the choice is not obvious, the CHANGELOG.md entry's lead paragraph says why, and what an upgrading deployment has to do.

  4. Keep versions synchronized across:

    • @pyproject.toml
    • @manifest.json
    • @server.json
    • OCI image tag in @server.json
  5. Promote ## [Unreleased] in @CHANGELOG.md to ## [X.Y.Z] - YYYY-MM-DD and append the dated entry to ROADMAP's execution log. Never rewrite older released entries.

  6. Run uv lock so uv.lock matches the new package metadata and dependencies.

  7. Create a git commit for the release preparation. First line: release: X.Y.Z, the title every release since 1.3.0 has used (CLAUDE.md and docs/architecture*.md name the same convention). Then bullet points with the important release notes.

  8. Other requirements: $ARGUMENTS

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.

  1. 25d ago Changed · +9 lines 6c2267da9bac
  2. 2mo ago First seen · 38 lines · 11 tokens per session scan A c26298001874

Subscribe to this mod's changes

release is a command published in the GitHub repository dlbolshov/yandex-wiki-search-mcp (7 stars, last pushed 25d ago), licensed Apache-2.0. It adds 11 tokens to every session and 550 once invoked, about $0.0000 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-31.

Related

release compared with commands from other repositories

release next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
releasedlbolshov/yandex-wiki-search-mcpCommand725d agoApache-2.0A11Claude Code
ia-changelogiliaal/whetstoneCommand352d agoMITA15Claude Code
releaseiliaal/whetstoneCommand352d agoMITA20Claude Code
repo-sprintqueelius/claude-anvilCommand24d agoMITA27Claude Code
releaseJoncik91/ucaiCommand282mo agoMITA11Claude Code
guardarMazalucas/El-DT-Lightweight-ArmyCommand4yesterdayMITA0Claude Code
run-releasealirezarezvani/claude-code-skill-factoryCommand89511mo agoMITA11Claude Code