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/insight-services-apac/ingenious/version-bumpgit clone --depth 1 https://github.com/Insight-Services-APAC/ingeniousWrote 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/insight-services-apac/ingenious/version-bump)<a href="https://agentmods.dev/commands/insight-services-apac/ingenious/version-bump"><img src="https://agentmods.dev/badge/commands/insight-services-apac/ingenious/version-bump.svg" alt="Measured on agentmods" 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.00000 | $0.00837 |
| Opus 5 | $0.00000 | $0.00418 |
| Sonnet 5 | $0.00000 | $0.00167 |
| Haiku 4.5 | $0.00000 | $0.00084 |
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 yesterday.
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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version Bump and Release Workflow
Objective
Increment the patch version (vX.Y.Z to vX.Y.(Z+1)), create a pull request, merge it, and publish a new release.
Workflow Steps
1. Version Detection and Update
-
Find current version: Search for version references in:
pyproject.toml(version field)package.json(version field)src/__init__.pyor<package>/__init__.py(version attribute)- Any other files containing version strings
-
Calculate new version: Increment the patch number (e.g., v0.2.7 to v0.2.8)
-
Update all version references: Replace all occurrences of the old version with the new version across all identified files
-
Verify changes: Confirm all version references have been updated correctly
2. Pull Request Creation
Run the /pr-create command to create a pull request with:
- Title format: "Bump version to vX.Y.Z"
- Description: "Update version from vX.Y.Z to vX.Y.Z across all files"
3. Pull Request Merge
Run the /pr-merge command to:
- Merge the version bump PR
- Run complete quality assurance pipeline (tests, linting, type checking)
- Use
--adminflag if needed - Preserve all commits (no squash)
4. Release Creation
After successful merge:
Prepare comprehensive release notes:
- Run
git log <previous-version>..HEAD --onelineto see all commits since last release - Run
git diff <previous-version>..HEAD --statto see all changed files - Categorize changes into sections:
- Features: New functionality added
- Improvements: Enhancements to existing features
- Bug Fixes: Issues resolved
- Documentation: Documentation updates
- Internal: Refactoring, tests, configuration changes
- List all significant changes with brief descriptions
- Note any breaking changes or migration requirements
Create release:
gh release create vX.Y.Z \
--title "Release vX.Y.Z" \
--notes "$(cat <<'EOF'
## Summary
Brief overview of release
## Changes
### Features
- Feature 1
### Improvements
- Improvement 1
### Bug Fixes
- Fix 1
### Documentation
- Doc update 1
### Internal
- Internal change 1
## Breaking Changes
Note any breaking changes or none
EOF
)" \
--target main
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.
- yesterday First seen · 124 lines · 0 tokens per session scan A efc47c29d8c2
version-bump is a command published in the GitHub repository Insight-Services-APAC/ingenious (24 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 837 tokens. 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-04.
Other commands, from other repositories
CHANGELOG
Command "CHANGELOG" from bytedance/UI-TARS-desktop, covering 0.4.0 2024-12-10 - add logging, 1.2.29, 1.2.28, 1.2.26 and 1.2.25.
chunkhound-release-notes
Generate release notes for a ChunkHound production release.
OpenSpec: Archive
Archive a deployed OpenSpec change and update specs.
release-notes
Draft curated release notes for a milestone release.
/release
Release a new version — updates CHANGELOG, pyproject.toml, creates git tag, and pushes.
bump-plugin
Bump changed plugin and marketplace version.