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/deepbluecoding/mcp-replay-dota2/release-versionnpx skills add DeepBlueCoding/mcp-replay-dota2 --skill release-versiongit clone --depth 1 https://github.com/DeepBlueCoding/mcp-replay-dota2Wrote 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/deepbluecoding/mcp-replay-dota2/release-version)<a href="https://agentmods.dev/skills/deepbluecoding/mcp-replay-dota2/release-version"><img src="https://agentmods.dev/badge/skills/deepbluecoding/mcp-replay-dota2/release-version.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.00122 | $0.01222 |
| Opus 5 | $0.00061 | $0.00611 |
| Sonnet 5 | $0.00024 | $0.00244 |
| Haiku 4.5 | $0.00012 | $0.00122 |
Grade A, and why
release-version 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release mcp-replay-dota2
release.yml is triggered ONLY by pushing a tag matching v*. It HARD-FAILS the build if the tag
version != pyproject.toml [project].version. Get these aligned before pushing or the whole run
dies.
Current version is 1.2.0 in BOTH [project].version AND [tool.commitizen].version. The
commitizen version_files is a single regex (pyproject.toml:^version) that matches BOTH
line-anchored version lines, so cz bump rewrites both at once — keep them aligned.
Workflow
- Pick the version. For a prerelease use a PEP440 suffix (
.dev,aN,bN,rcN) — these route to TestPyPI, NOT PyPI. Stable versions go to PyPI + GitHub release + Docker. - Bump with commitizen (preferred — keeps
pyproject.tomlandCHANGELOG.mdin sync and creates thev$versiontag):
commitizen config:uv run cz bump # auto-detects bump from conventional commits # or force: uv run cz bump --increment PATCH|MINOR|MAJORcz_conventional_commits,tag_format=v$version,update_changelog_on_bump=true,changelog_file=CHANGELOG.md, incremental. The singleversion_filesregex rewrites both[project].versionand[tool.commitizen].version. - Verify tag == version (release.yml does exactly this and exits 1 on mismatch):
The two must be identical (tag without the leadinguv run python -c "import tomllib; print(tomllib.load(open('pyproject.toml','rb'))['project']['version'])" git describe --tags --abbrev=0v). - Run the local CI gate — release.yml re-runs ruff + mypy before building, so failures there
waste a tagged run:
uv run ruff check src/ tests/ dota_match_mcp_server.py uv run mypy src/ dota_match_mcp_server.py --ignore-missing-imports uv run pytest - Update
docs/changelog.md(Keep-a-Changelog, user-facing) for release notes if not already done.CHANGELOG.mdis the commitizen-generated one — letcz bumpown it. - Push the tag to trigger the release pipeline (only when the user asks to push):
git push origin master git push origin v<version> - Ad-hoc image only: use the
docker-manual.ymlworkflow (workflow_dispatch, inputversion) — pushes an image without a full release.
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.
- 5d ago First seen · 85 lines · 122 tokens per session scan A 3df471657efc
release-version is a skill published in the GitHub repository DeepBlueCoding/mcp-replay-dota2 (2 stars, last pushed 3mo ago), licensed MIT. It adds 122 tokens to every session and 1,222 once invoked, about $0.0006 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.
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.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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…