Borrowing it
Nothing to install: this file belongs to APonkratov/yandex-tracker-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.
curl -O https://raw.githubusercontent.com/APonkratov/yandex-tracker-mcp/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/APonkratov/yandex-tracker-mcpWrote 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/commands/aponkratov/yandex-tracker-mcp/release)<a href="https://agentmods.dev/commands/aponkratov/yandex-tracker-mcp/release"><img src="https://agentmods.dev/badge/commands/aponkratov/yandex-tracker-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.
<a href="https://agentmods.dev/commands/aponkratov/yandex-tracker-mcp/release"><img src="https://agentmods.dev/badge/commands/aponkratov/yandex-tracker-mcp/release.svg" alt="Reviewed on agentmods" width="80" 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.00007 | $0.00510 |
| Opus 5 | $0.00003 | $0.00255 |
| Sonnet 5 | $0.00001 | $0.00102 |
| Haiku 4.5 | $0.00001 | $0.00051 |
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 10d 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.
This is a copy
100% identical to release — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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 the project. You may spin parallel tasks if you need as long as changed files don't overlap.
Instructions
- Make sure to fix all linter problems with
taskcommand. - Make sure that @README.md is up to date with current code structure, specification, architecture, features, environment variables. Make sure to also update the translated version at @README_ru.md. Also if there are new tools added to the project - make sure they are documented in @README.md, @README_ru.md, @manifest.json
- If it is a minor change or a patch, update the version in @pyproject.toml accordingly. While major version is still 0.x, any minor changes should be reflected at increase of patch part, and any big changes - in the minor part of the version.
- Always make sure that the version in @manifest.json and @server.json are the same as in @pyproject.toml. Also don't forget to update the version
identifierof oci image in @server.json - it should match the new version. - Make sure @CHANGELOG.md is up to date with the latest changes. Changes may be collected through git history since last git tag or current unstaged changes. Always add a new version to the @CHANGELOG.md, even if it is a patch release. Never edit previous versions.
- Call
uv sync --all-extras --all-packagesto update uv.lock file. - Make a git commit reflecting changes currently made. The first line must be a commit changes summary in short sentence (don't use version bump as a commit headline). Then using bullet points highlight main changes made.
- Other requirements: $ARGUMENTS
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.
- 10d ago First seen · 26 lines · 7 tokens per session scan A e38a0a9c48c1
release is a command published in the GitHub repository APonkratov/yandex-tracker-mcp (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 510 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to release, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.