Borrowing it
Nothing to install: this file belongs to ricardoquesada/regenerator2000. 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/ricardoquesada/regenerator2000/main/.agent/skills/bump-version/SKILL.mdgit clone --depth 1 https://github.com/ricardoquesada/regenerator2000Wrote 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/ricardoquesada/regenerator2000/bump-version)<a href="https://agentmods.dev/skills/ricardoquesada/regenerator2000/bump-version"><img src="https://agentmods.dev/badge/skills/ricardoquesada/regenerator2000/bump-version.svg" alt="Measured on agentmods" 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.00019 | $0.00496 |
| Opus 5 | $0.00010 | $0.00248 |
| Sonnet 5 | $0.00004 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00050 |
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 8d 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.
What it actually says
Bump Version Skill
Use this skill when the user requests to bump the project version (e.g., "bump version to v0.8.0" or "prepare release x.y.z").
1. Verify the New Version
Ensure the user provided a valid semantic version (e.g., 0.8.0). If they didn't specify one, determine the correct next version based on recent changes (major/minor/patch) or ask the user for clarification.
2. Update Cargo.toml files
Update the version field in the following files:
- Root
Cargo.toml:- Update
[package].version. - Update
regenerator2000-coreandregenerator2000-tuiversions in the[dependencies]section.
- Update
crates/regenerator2000-core/Cargo.toml:- Update
[package].version.
- Update
crates/regenerator2000-tui/Cargo.toml:- Update
[package].version. - Update
regenerator2000-coreversion in the[dependencies]section.
- Update
3. Review Recent Changes
Run the following command to get a list of commits since the last tag:
git log $(git describe --tags --abbrev=0)..HEAD --oneline
Review the commit messages to understand the scope of what features, fixes, and other changes are included in this release.
4. Update CHANGELOG.md
In CHANGELOG.md:
- Create a new header section for the new version directly below the project headers or the
[Unreleased]section. - Use the format:
## [x.y.z] - YYYY-MM-DDusing the current date. - Categorize the changes based on the commit history into the appropriate sections, such as:
### Features### Fixes### Changes### Refactor / Internal### Documentation- etc.
- Ensure the descriptions are concise and match the existing changelog formatting conventions.
5. Verify and Notify User
Summarize the updates made and notify the user that Cargo.toml and CHANGELOG.md have been successfully updated for the new version.
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.
- 8d ago First seen · 55 lines · 19 tokens per session scan A b74cde28bd1f
bump-version is a skill published in the GitHub repository ricardoquesada/regenerator2000 (164 stars, last pushed 13d ago), licensed Apache-2.0. It adds 19 tokens to every session and 496 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.
Other skills, from other repositories
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release-and-publish
Ship a release end-to-end across every registry this project targets (npm, MCP Registry). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already complete — this skill is the post-wrapup…
release-management
Tag a commit, publish a GitHub release, and read, correct or withdraw the tags and releases already there.
release-versioning
Discipline for release classification, version bumps, and changelogs, Conventional Commits classify the release range, SemVer computes the version from those commits, Keep a Changelog renders the result. Use when the user asks to cut a release, bump a version, write a changelog, decide if a change is a…
hmem-release
Pre-publish checklist for hmem: skills synced, version bumped, tests green, nothing forgotten. Use before npm publish or when the user says 'release', 'publish', 'push a release', or 'neue Version'.
safe-deployment
Discipline for shipping changes reversibly, decouple deploy (code reaches production) from release (users see it) with feature flags, roll out progressively, and define the automated rollback trigger before shipping, not during the incident. Use when the user asks how to deploy a risky change, choose between…