Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Emasoft/claude-plugins-validation/plugin install claude-plugins-validationWrote 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/emasoft/claude-plugins-validation/cpv-bump-version)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-bump-version"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-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/emasoft/claude-plugins-validation/cpv-bump-version"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-bump-version.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.00067 | $0.00979 |
| Opus 5.5 | $0.00027 | $0.00392 |
| Sonnet 5.5 | $0.00013 | $0.00196 |
| Haiku 4.5 | $0.00007 | $0.00098 |
Grade A, and why
cpv-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 1mo 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cpv-bump-version
Overview
Bumps the plugin version AND runs the full publish pipeline (TRDD-bbff5bc5 — single entry point). publish.py is the canonical entry point — it bumps the version in plugin.json + pyproject.toml + __version__ vars, refreshes the README badge, regenerates the CHANGELOG, refreshes .plugin-self-hashes.json (if present), commits + tags + pushes, then creates the GitHub release. Every gate must pass before any push — no CLI skip flags exist; the few sanctioned env toggles (e.g. PLUGIN_SKIP_GITHUB_INTEGRITY) are listed in publish.py --help and are test-pinned. Loaded dynamically via cpv-the-skills-menu, reached via the Manage → Bump version menu branch.
Prerequisites
uvon PATH- Clean git working tree (no uncommitted changes)
ghCLI authenticated for GitHub release creation- Network access for git push / GitHub API
PLUGIN_SKIP_GITHUB_INTEGRITY=1NOT set unless intentionally skipping integrity gate
Instructions
- Confirm the working tree is clean (
git status). - Choose a bump level:
--patch,--minor, or--major. - Always preview first with
--dry-runto confirm the new version, CHANGELOG entry, and gate-pass list. - Run the real invocation;
publish.pyenforces every quality gate before push. - If any gate fails, fix the underlying issue and re-run —
publish.pyis idempotent (interrupted runs resume cleanly). - After publish, confirm the GitHub release URL was printed.
Copy this checklist and track your progress:
- Working tree clean
- Bump level chosen
-
--dry-runreviewed - Real
publish.pyinvocation executed - All gates passed
- GitHub release URL captured
Output
- Updated
plugin.json::version,pyproject.toml::version,__version__vars - Refreshed README version badge
- Regenerated
CHANGELOG.mdentry - Git commit + tag + push
- GitHub release published
Error Handling
| Error | Resolution |
|---|---|
| Gate failure (lint/test/validate) | Fix the underlying issue, re-run (publish.py resumes idempotently) |
| Dirty working tree | git stash or commit changes before bumping |
gh auth not set up |
Run gh auth login first |
| Network timeout on push | Re-run; publish.py picks up where it left off |
| Version conflict on push | Pull first, resolve, re-run |
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.
- 1mo ago Changed 428e79250000
- 1mo ago First seen · 89 lines · 67 tokens per session scan A e80332c35513
cpv-bump-version is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 3d ago), licensed MIT. It adds 67 tokens to every session and 979 once invoked, about $0.0003 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-31.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.