Borrowing it
Nothing to install: this file belongs to reggiechan74/JobOps. 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/reggiechan74/JobOps/main/.claude/commands/version-bump.mdgit clone --depth 1 https://github.com/reggiechan74/JobOpsWrote 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/commands/reggiechan74/jobops/version-bump)<a href="https://agentmods.dev/commands/reggiechan74/jobops/version-bump"><img src="https://agentmods.dev/badge/commands/reggiechan74/jobops/version-bump/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/commands/reggiechan74/jobops/version-bump"><img src="https://agentmods.dev/badge/commands/reggiechan74/jobops/version-bump.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.00017 | $0.01505 |
| Opus 5.5 | $0.00007 | $0.00602 |
| Sonnet 5.5 | $0.00003 | $0.00301 |
| Haiku 4.5 | $0.00002 | $0.00151 |
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 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/version-bump
Bump the JobOps version consistently across every file that carries it, and add a new CHANGELOG entry categorized by release type.
Inputs
$ARGUMENTS should contain:
- Release type (required, first token):
patch|minor|majorpatch→ bug fix (X.Y.Z → X.Y.Z+1) → CHANGELOG section: Fixedminor→ new feature, backwards-compatible (X.Y.Z → X.Y+1.0) → CHANGELOG section: Added / Changedmajor→ breaking change (X.Y.Z → X+1.0.0) → CHANGELOG section: Changed — BREAKING
- Description (optional, everything after the type): short summary of the change. If omitted, derive one from the current git diff and recent conversation context.
If $ARGUMENTS is empty or the release type is missing/invalid, ask the user via AskUserQuestion which type to apply before proceeding.
Files that carry the version
These eight files must all be bumped to the same version in a single pass. They split into Claude Code manifests, Codex manifests (the .codex-plugin/ + .agents/ pair added for Codex compatibility), and the package/README. If any of these paths no longer exists or new version-bearing files have been added, surface the discrepancy and ask before proceeding.
| File | Field |
|---|---|
package.json |
"version": "X.Y.Z" |
.claude-plugin/marketplace.json |
metadata.version (Claude Code marketplace) |
.agents/plugins/marketplace.json |
metadata.version (Codex marketplace) |
plugins/jobops/.claude-plugin/plugin.json |
"version": "X.Y.Z" (Claude Code manifest) |
plugins/jobops/.codex-plugin/plugin.json |
"version": "X.Y.Z" (Codex manifest) |
plugins/jobops-ic/.claude-plugin/plugin.json |
"version": "X.Y.Z" (Claude Code manifest) |
plugins/jobops-ic/.codex-plugin/plugin.json |
"version": "X.Y.Z" (Codex manifest) |
README.md |
**Version X.Y.Z** line near the top |
npm test validates that the Codex marketplace and both Codex manifests match — run it after bumping to catch any Codex file you missed.
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 First seen · 80 lines · 17 tokens per session scan A 29d7b7883bb4
version-bump is a command published in the GitHub repository reggiechan74/JobOps (26 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 1,505 once invoked, about $0.0001 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-30.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
rally-merge-pr
You are merging the current branch's PR and syncing the feature branch with main. Follow each step exactly.