Borrowing it
Nothing to install: this file belongs to anantjain-xyz/symphony-rust. 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/anantjain-xyz/symphony-rust/main/.codex/skills/bump-version/SKILL.mdgit clone --depth 1 https://github.com/anantjain-xyz/symphony-rustWrote 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/anantjain-xyz/symphony-rust/bump-version)<a href="https://agentmods.dev/skills/anantjain-xyz/symphony-rust/bump-version"><img src="https://agentmods.dev/badge/skills/anantjain-xyz/symphony-rust/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/anantjain-xyz/symphony-rust/bump-version"><img src="https://agentmods.dev/badge/skills/anantjain-xyz/symphony-rust/bump-version.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.00067 | $0.00691 |
| Opus 5 | $0.00034 | $0.00345 |
| Sonnet 5 | $0.00013 | $0.00138 |
| Haiku 4.5 | $0.00007 | $0.00069 |
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 10d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bump Version
Objective
Update the project release version consistently while avoiding dependency upgrades, unrelated formatting churn, and broad search-and-replace mistakes.
Workflow
-
Inspect the repo state first.
- Run
git status --short. - Locate likely version files with
rg --files -g 'Cargo.toml' -g 'Cargo.lock' -g 'package.json' -g '*lock*' -g 'pyproject.toml' -g 'VERSION' -g '*version*'. - Search for release-version declarations with
rg -n '^version\s*=|"version"\s*:|__version__|VERSION'.
- Run
-
Determine the target version.
- Use the user-provided target version when present.
- If the user only says to bump the version, default to the next patch version and say that assumption in an update or final response.
- If discovered release surfaces disagree and the correct source of truth is not obvious, stop and ask before editing.
-
Identify release surfaces.
- Prefer explicit project/app/package versions:
Cargo.toml[workspace.package]or[package], Taurisrc-tauri/Cargo.toml,src-tauri/tauri.conf.json, rootpackage.json,pyproject.toml, standaloneVERSIONfiles, and release scripts that embed the app version. - Include lockfiles only for local package entries or root importer metadata that represent the project version.
- Do not update dependency versions, checksums, generated build outputs, bundle artifacts, or release tags unless the user explicitly asks.
- Prefer explicit project/app/package versions:
-
Apply the smallest consistent edit.
- Use
apply_patchfor hand edits. - Avoid blind repo-wide replacement. Exact old-version matches can include dependency versions such as
0.1.65. - For Cargo, update workspace and package manifest versions, then keep
Cargo.locklocal package entries in sync. Runningcargo metadata --locked --no-deps --format-version 1is a good validation pass. - For JavaScript package lockfiles, prefer the repo package manager's lockfile-only command only if it will not upgrade dependencies; inspect the diff afterward.
- Use
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 46 lines · 67 tokens per session scan A 3c005a004a28
bump-version is a skill published in the GitHub repository anantjain-xyz/symphony-rust (11 stars, last pushed 27d ago), licensed MIT. It adds 67 tokens to every session and 691 once invoked, about $0.0003 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
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.