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/parkerm2/create-claude-workflow/bump-versiongit clone --depth 1 https://github.com/ParkerM2/create-claude-workflowWhat 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.00019 | $0.01241 |
| Opus 5 | $0.00010 | $0.00620 |
| Sonnet 5 | $0.00004 | $0.00248 |
| Haiku 4.5 | $0.00002 | $0.00124 |
Grade A, and why
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 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bump-version — Automated Release
Automates the full release process from RELEASING.md. Bumps version across all files, writes changelog, commits, tags, pushes, and updates the marketplace repo.
Phase 1: Determine Version
- Read the current version from
.claude-plugin/plugin.json(the"version"field). - Ask the user which bump type to apply:
- Patch (X.Y.Z → X.Y.Z+1) — bug fixes, minor tweaks
- Minor (X.Y.Z → X.Y+1.0) — new features, non-breaking changes
- Major (X.Y.Z → X+1.0.0) — breaking changes
- Custom — user specifies exact version string
- Compute the new version string.
Phase 2: Generate Changelog Entry
- Run
git logto find all commits since the last version tag:# Find the latest version tag LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "") # Get commits since that tag (or all commits if no tag) if [ -n "$LAST_TAG" ]; then git log "${LAST_TAG}..HEAD" --oneline --no-merges else git log --oneline --no-merges -20 fi - Categorize commits into Added, Changed, Fixed, Removed sections based on commit message prefixes:
feat:/add:→ Addedfix:→ Fixedrefactor:/chore:/perf:→ Changedremove:/delete:→ Removed- Other → Changed
- Draft a changelog entry using today's date and present it to the user for review.
- User approves or edits the changelog entry.
Phase 3: Apply Version Bump
Update the version in these files (all must match):
.claude-plugin/plugin.json— update the"version"fieldCHANGELOG.md— prepend the new entry at the top (below the# Changelogheader, above the previous version entry). Include the### Updateblock:
/plugin update claude-workflow@claude-workflow-marketplace### Updatemarketplace/.claude-plugin/marketplace.json— update BOTHmetadata.versionANDplugins[0].version
Phase 4: Commit, Tag, and Push Plugin Repo
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 · 130 lines · 19 tokens per session scan A 59f3d7067459
bump-version is a command published in the GitHub repository ParkerM2/create-claude-workflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 1,241 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-31.
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.