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 skills add LucasSantana-Dev/sharekit --skill version-bumpgit clone --depth 1 https://github.com/LucasSantana-Dev/sharekitWrote 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/lucassantana-dev/sharekit/version-bump)<a href="https://agentmods.dev/skills/lucassantana-dev/sharekit/version-bump"><img src="https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/version-bump.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.00021 | $0.00738 |
| Opus 5 | $0.00010 | $0.00369 |
| Sonnet 5 | $0.00004 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
version-bump 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 3d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automate version bumping across an npm monorepo (npm workspaces), promote CHANGELOG entries, and open a PR with auto-merge enabled.
Scope note (2026-07-23): in release-please repos (the default), release-please owns version bumping and changelog promotion via its release PR — do not run this skill there. It remains for repos without release-please configured.
Prerequisites
- Active git repo with root
package.jsonand npm workspaces inpackages/*/package.json CHANGELOG.mdexists with[Unreleased]section- Git repo is clean (no unstaged changes)
- GitHub CLI (
gh) is installed and authenticated - Current branch is
main(ormaster)
Workflow
- Validate version argument: Ensure
NEXT_VERSIONmatches semantic versioning (e.g.,2.7.0) - Check git state: Fail if uncommitted changes exist or if
NEXT_VERSIONis already tagged - Bump versions: Update root
package.jsonand allpackages/*/package.jsontoNEXT_VERSION - Promote CHANGELOG: Move
[Unreleased]section header to[NEXT_VERSION] - YYYY-MM-DD(today's date) - Create branch:
chore/bump-NEXT_VERSION - Commit: Message =
chore: bump version to NEXT_VERSION - Push: Push the branch to origin
- Open PR: Use
gh pr create --auto-mergewith standard description - Verify: Confirm tag does not exist before proceeding; never force-push
Safety rules
- No force-push: Uses
git push origin <branch>only - Tag conflict check: Stop if git tag
vNEXT_VERSION(orNEXT_VERSION) exists - Clean repo only: Fail if
git statusshows changes - Reversible: If PR creation fails, user can manually delete the branch
Usage examples
# Bump to 2.7.0
/version-bump 2.7.0
# In a monorepo
/version-bump 1.15.3
Output / Evidence
- Confirm root and all package
package.jsonfiles were updated - Confirm CHANGELOG entry was promoted with today's date
- Link to the opened PR with auto-merge status
Implementation hints
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.
- 3d ago First seen · 72 lines · 21 tokens per session scan A 9f68e1babecf
version-bump is a skill published in the GitHub repository LucasSantana-Dev/sharekit (1 stars, last pushed 6d ago), licensed MIT. It adds 21 tokens to every session and 738 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-09-03.
Other skills, from other repositories
do
Work an increment task by task through the ledger: task next, claim, implement, commit, task done with evidence. Use when saying "implement", "start working", or "continue increment".
creating-issues-and-pull-requests
Use when creating GitHub pull requests or issues with template compliance. Triggers: 'create a PR', 'open a pull request', 'file an issue', 'create issue'. Also invoked by finishing-a-development-branch. NOT for: deciding whether to merge or PR (use finishing-a-development-branch).
work
Handle issue/PR work items with worktree isolation. Triggered by "/work [issuelink|description]" to start focused work.
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".
atomic-git-discipline
Compressed commit message and PR body generator. Cuts noise from both while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious; PR bodies state only what the diff can't show, 120 words max. Use when user says "write a commit", "commit message", "generate…
commit-msg
You receive a git diff of staged changes via stdin. Generate a commit message.