wyoming_openai: Skill for Claude Code

.agents/skills/bump-version/SKILL.md

bump-version is a skill for Claude Code from roryeckel/wyoming_openai. It costs 15 tokens per session (375 once invoked), scanned A, original, Apache-2.0.

A workflow for increasing the version number of the wyoming-openai package according to the type of change made.

In plain words
What is it for?
Use it to estimate or apply a version bump, update pyproject.toml and the README, review recent Git changes, and prepare the follow-up commit and tag.
Why use it?
It reduces mistakes when updating the package version and related documentation, while helping decide whether a change is a patch, minor, or major release.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is roryeckel/wyoming_openai's own configuration. It tells Claude Code how to work on wyoming_openai 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 wyoming_openai configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/roryeckel/wyoming_openai/main/.agents/skills/bump-version/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/roryeckel/wyoming_openai

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 bump-version

README.md
[![agentmods](https://agentmods.dev/badge/skills/roryeckel/wyoming_openai/bump-version/github.svg)](https://agentmods.dev/skills/roryeckel/wyoming_openai/bump-version)
Your own site
<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.

agentmods 80×15 button for bump-version

Your own site · 80×15
<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>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 375 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00015 $0.00375
Opus 5 $0.00008 $0.00187
Sonnet 5 $0.00003 $0.00075
Haiku 4.5 $0.00002 $0.00038

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

Security

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.

.agents/skills/bump-version/SKILL.md · 33 lines

What it actually says

Bump version $ARGUMENTS.

For releases off main, prefer the GitHub Actions Bump Version workflow (.github/workflows/bump-version.yml) — it performs the same edits, opens a labeled PR, and chains into the draft-release workflow on merge. Use this skill locally when working off a non-main branch or when you need estimate mode.

Steps:

  1. Read current version from pyproject.toml (line containing version = "x.y.z")
  2. If no argument provided, default to minor bump
  3. If argument is estimate, analyze changes since last tag to determine bump type:
    • Use git log and git diff to 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
  4. 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
  5. Update version in:
    • pyproject.toml: Update version = "x.y.z" line
    • README.md: Update version in Docker tagging section
  6. Display summary: old version → new version, files updated
  7. Remind user to commit and tag: git tag vx.y.z
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. 10d ago First seen · 33 lines · 15 tokens per session scan A 61b7ac660d44

Subscribe to this mod's changes

bump-version is a skill published in the GitHub repository roryeckel/wyoming_openai (209 stars, last pushed 2d ago), licensed Apache-2.0. It adds 15 tokens to every session and 375 once invoked, about $0.0001 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-30.

Related

Other skills, from other repositories

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

hashgraph-online/awesome-codex-plugins · 69 tokens

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.

Azure/GPT-RAG · 56 tokens

oss-maintainer

Run an open-source project's issue/PR/release loop like a careful human maintainer — triage to root cause, absorb community PRs before duplicating them, gate every merge, ship honest releases, and thank the people doing your QA for free.

debpalash/VoiceStudio · 55 tokens

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…

btfranklin/skills · 77 tokens

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.

hashgraph-online/awesome-codex-plugins · 33 tokens

pr-release-gate

Use for PR readiness, branch hygiene, checks, review feedback, release gates, publish readiness, and post-merge handoff. Do not push to main, merge with pending required checks, or mark release ready without evidence.

ASMN-96/ai-agents-skills-toolkit · 50 tokens