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 codebygarv/Ai-skills --skill semver-bump-advisorgit clone --depth 1 https://github.com/codebygarv/Ai-skillsWrote 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/codebygarv/ai-skills/semver-bump-advisor)<a href="https://agentmods.dev/skills/codebygarv/ai-skills/semver-bump-advisor"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/semver-bump-advisor/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/codebygarv/ai-skills/semver-bump-advisor"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/semver-bump-advisor.svg" alt="Reviewed on agentmods" width="80" 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.00029 | $0.00379 |
| Opus 5 | $0.00015 | $0.00189 |
| Sonnet 5 | $0.00006 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
semver-bump-advisor 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.
What it actually says
Purpose
Analyze git commit histories (Conventional Commits), API changes, and export diffs to determine the exact Semantic Versioning (SemVer 2.0.0) bump required (PATCH, MINOR, or MAJOR) with full rationale.
When to Use
- Preparing a new library or package release (npm, PyPI, Crates.io, Go modules).
- Configuring automated release tools (semantic-release, changesets, release-please).
- Determining if a refactoring change introduced an accidental breaking change.
What to Analyze
- MAJOR Bump Triggers:
- Renaming or removing exported functions/types/constants.
- Changing argument order or making optional parameters required.
- Bumping minimum runtime engine requirements (e.g. Node 16 $ ightarrow$ 20).
- MINOR Bump Triggers:
- Adding new backwards-compatible exported functions, options, or endpoints.
- Deprecating an existing feature without removing it.
- PATCH Bump Triggers:
- Backwards-compatible bug fixes and internal performance refactors.
- Documentation and non-functional dependency updates.
Output Format
- Recommended Version: e.g.,
1.4.2$ ightarrow$2.0.0(MAJOR). - SemVer Justification: Point-by-point commit analysis mapping changes to SemVer rules.
- Breaking Change Migration Guide: If MAJOR, clear instructions for consumers to upgrade.
Avoid
- Bumping MINOR or PATCH when an exported interface signature was altered.
- Releasing breaking changes under a PATCH release.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 39 lines · 29 tokens per session scan A 0c53d76ec69f
semver-bump-advisor is a skill published in the GitHub repository codebygarv/Ai-skills (25 stars, last pushed 19d ago), licensed MIT. It adds 29 tokens to every session and 379 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
git-pr
PR and MR workflows for GitHub (gh) and GitLab (glab). Creation, review comment handling, thread resolution, review state queries, merging, cost-aware bot review rounds (GitHub: Copilot, CodeRabbit), and Copilot code review configuration (rulesets, custom instructions, billing). Use when creating PRs/MRs, addressing…
git-project
GitHub Projects (v2) setup and management via gh CLI + GraphQL: organize a repo's issues into epics with native sub-issues, drive a board Status flow (Todo -> In Progress -> Done), set Project Priority, classify with native issue Types (Task/Bug/Feature) instead of labels, scope work with milestones (incl. resolving…
git-commit
Conventional Commits format for git commits and PR/MR titles. Type prefixes, scope rules, breaking change syntax, and commit message structure. Use when committing changes, writing commit messages, creating PR/MR titles, or formatting squash merge messages. Not for PR workflows (git-pr), CI/CD status (git-ci), or git…
ds-ship
Ship orchestrator — classify the project, pick a mode (improve/release/launch/maintain), delegate only the skills the project's signals justify, consolidate findings, produce an audit report. Use for an end-to-end audit or ship pipeline across multiple skills.
ds-freeze
Release scope triage — decide which features ship this release vs defer to backlog, then file/implement the kept set and sync docs to match. Use when a release has grown too complex to finish or polish everything and the team needs to cut scope deliberately.
ds-release
Release cutter — version from the commits, dated CHANGELOG section, every version surface bumped, project check green, local release commit + annotated tag; every publishing step (push, GitHub release, registry, store) handed to the human with the exact command. Use when a release is to be cut.