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 agentmods add commands/reggiechan74/jobops/version-bumpgit clone --depth 1 https://github.com/reggiechan74/JobOpsWhat 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 | $0.00017 | $0.01505 |
| Opus 5 | $0.00009 | $0.00753 |
| Sonnet 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 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 — 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.
- 3d ago First seen · 80 lines · 17 tokens per session scan A 29d7b7883bb4
version-bump is a command published in the GitHub repository reggiechan74/JobOps (25 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 1,505 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 commands, from other repositories
review-renovate
Review and merge renovate PRs with automerge configuration updates.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
release
Create a full stable release for the project. Optionally pass a title suffix (e.g., "Template Presets Fix") or extra notes.
SHIP_RELEASE
Ship the active release/X.Y.Z — build the installer, merge to main, tag, push, and publish the GitHub release. Run after /prerelease passes.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
release
The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.