Borrowing it
Nothing to install: this file belongs to asta-nguyen/kamehadb. 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/asta-nguyen/kamehadb/main/.agents/skills/bump-version/SKILL.mdgit clone --depth 1 https://github.com/asta-nguyen/kamehadbWrote 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/asta-nguyen/kamehadb/bump-version)<a href="https://agentmods.dev/skills/asta-nguyen/kamehadb/bump-version"><img src="https://agentmods.dev/badge/skills/asta-nguyen/kamehadb/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/asta-nguyen/kamehadb/bump-version"><img src="https://agentmods.dev/badge/skills/asta-nguyen/kamehadb/bump-version.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00071 | $0.01137 |
| Opus 5 | $0.00036 | $0.00568 |
| Sonnet 5 | $0.00014 | $0.00227 |
| Haiku 4.5 | $0.00007 | $0.00114 |
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 12d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bump Version
This workflow updates the KamehaDB app version across all files that contain it, and updates the CHANGELOG.
Version locations
The version string must be updated in all of these files (they must stay in sync):
| # | File | Field |
|---|---|---|
| 1 | package.json |
"version" |
| 2 | apps/desktop/package.json |
"version" |
| 3 | apps/sidecar/package.json |
"version" |
| 4 | packages/shared/package.json |
"version" |
| 5 | apps/desktop/src-tauri/tauri.conf.json |
"version" |
| 6 | apps/desktop/src-tauri/Cargo.toml |
version = "..." under [package] |
Note:
landing/package.jsonhas its own independent version (0.1.0) — do NOT touch it.
Steps
1. Determine the new version
Run these commands to inspect recent commits since the last version:
# Show the current version
grep '"version"' package.json | head -1
# Show commits since the last version tag
git log --oneline $(git describe --tags --abbrev=0 2>/dev/null || echo HEAD~50)..HEAD --oneline 2>/dev/null || git log --oneline -30
Use Semantic Versioning rules:
- Patch (e.g.
1.4.0→1.4.1): bug fixes only, no new features. - Minor (e.g.
1.4.0→1.5.0): new features added, backward compatible. - Major (e.g.
1.4.0→2.0.0): breaking changes.
If the user specifies a version, use that. Otherwise, analyze the commit messages:
- Commits with
feat:orfeat(scope):→ at least a minor bump. - Commits with
fix:orfix(scope):only → patch bump. - Commits with
BREAKING CHANGEor!:→ major bump.
Ask the user to confirm the target version before proceeding.
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.
- 12d ago First seen · 140 lines · 71 tokens per session scan A 66f2fb1a665e
bump-version is a skill published in the GitHub repository asta-nguyen/kamehadb (14 stars, last pushed 11d ago), licensed Apache-2.0. It adds 71 tokens to every session and 1,137 once invoked, about $0.0004 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 skills, from other repositories
release
Cut a Memoria release. Version bump, CHANGELOG, CI workflows, Docker image. Use when publishing a new version.
git-expert
Expert-level Git version control with advanced workflows, branching strategies, and best practices for team collaboration. Use when the user mentions version control, collaboration, or workflow, or when the task involves Essential Git Commands, Advanced Git Techniques, Branching Strategies, or Conflict Resolution.
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
contrib-pr
Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.