Borrowing it
Nothing to install: this file belongs to roryeckel/wyoming_openai. 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/roryeckel/wyoming_openai/main/.agents/skills/bump-version/SKILL.mdgit clone --depth 1 https://github.com/roryeckel/wyoming_openaiWrote 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/roryeckel/wyoming_openai/bump-version)<a href="https://agentmods.dev/skills/roryeckel/wyoming_openai/bump-version"><img src="https://agentmods.dev/badge/skills/roryeckel/wyoming_openai/bump-version/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/roryeckel/wyoming_openai/bump-version"><img src="https://agentmods.dev/badge/skills/roryeckel/wyoming_openai/bump-version.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00015 | $0.00654 |
| Opus 5.5 | $0.00006 | $0.00262 |
| Sonnet 5.5 | $0.00003 | $0.00131 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
bump-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 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bump version $ARGUMENTS.
Releasing off main — dispatch the workflow
A release is prepared by the Bump Version GitHub Action, not by hand.
Do not edit pyproject.toml/README.md locally, and do not create the tag.
- Dispatch it (or Actions → Bump Version → Run workflow):
gh workflow run bump-version.yml -f bump_type=<patch|minor|major> - The Action runs the Home Assistant E2E gate, updates
pyproject.tomlandREADME.md, and opens a PR fromrelease/v<new>labeledrelease-bump. - Optionally set the GitHub release title on the PR body's
Release title:line (the version is appended automatically; blank defaults toRelease <new>), then merge the PR. The Draft Release workflow re-runs the E2E gate against the merge commit and creates the draft release with generated notes. - Publishing that draft release creates the
v<new>tag and fires the PyPI and Dockerlatestworkflows.
The Action fails if release/v<new> already exists on origin; delete a stale
release branch before re-dispatching. Use gh run watch <run-id> --exit-status
to follow it, then check the new PR with gh pr list.
Local fallback
Use the steps below only when working off a non-main branch, when the Action
is unavailable, or for estimate mode.
- Read current version from
pyproject.toml(line containingversion = "x.y.z") - If no argument provided, default to minor bump
- If argument is
estimate, analyze changes since last tag to determine bump type:- Use
git logandgit diffto review recent changes - patch: bug fixes, documentation, minor tweaks
- minor: new features, non-breaking enhancements
- major: breaking changes, API modifications
- Present recommendation to user for confirmation before proceeding
- Use
- Calculate new version:
- patch: x.y.z → x.y.(z+1)
- minor: x.y.z → x.(y+1).0
- major: x.y.z → (x+1).0.0
- Update version in:
pyproject.toml: Updateversion = "x.y.z"lineREADME.md: Update both Docker tagging examples (thex.y.zandx.ytags in section "Docker Tags")
- Display summary: old version → new version, files updated
- Commit the edits. Tag
vx.y.zonly if you are building release artifacts outside the workflow.
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 Changed · +24 lines 9391080065cd
- 2mo ago First seen · 33 lines · 15 tokens per session scan A 61b7ac660d44
bump-version is a skill published in the GitHub repository roryeckel/wyoming_openai (225 stars, last pushed 9d ago), licensed Apache-2.0. It adds 15 tokens to every session and 654 once invoked, about $0.0001 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-30.
Other skills, from other repositories
voicestudio-maintainer
Triage GitHub issues, review contributor pull requests, diagnose CI, and prepare explicitly requested releases for VoiceStudio's Electron desktop app and Python backend. Use for repository maintenance work, not ordinary VoiceStudio audio generation.
git-workflow
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.
writing-modpack-changelog
Use when cutting a modpack release. Creates /docs/release-changelog.md if absent; appends a new version section with grouped changes. Triggers - 'cut a release', 'release notes', 'changelog', 'v1.2.3 changes', 'what changed since last version'.
multi-repo-release
Prepares and validates GPT-RAG umbrella and multi-repository releases. Use whenever work involves release preparation, semantic versions, release branches, manifest or component pins, changelog release entries, tags, GitHub Release notes, or AI Landing Zone release alignment.
publish-npm-package
Configure or troubleshoot npm package publication with GitHub Actions and npm Trusted Publishing. Use this skill for JavaScript or TypeScript packages. Also use it for the npm package in a mixed-language repository. Do not use it for applications or repositories without an npm package. Do not use it for generic CI…
ship
Finish already-implemented work for merge or release - verify before claiming done, write commits and PR descriptions, plan releases and rollbacks. Use when wrapping up a branch or deciding how to integrate it. Not for writing code.