Borrowing it
Nothing to install: this file belongs to leochiu-a/elden-ring-github. 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/leochiu-a/elden-ring-github/main/.claude/skills/bump-version/SKILL.mdgit clone --depth 1 https://github.com/leochiu-a/elden-ring-githubWrote 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/leochiu-a/elden-ring-github/bump-version)<a href="https://agentmods.dev/skills/leochiu-a/elden-ring-github/bump-version"><img src="https://agentmods.dev/badge/skills/leochiu-a/elden-ring-github/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/leochiu-a/elden-ring-github/bump-version"><img src="https://agentmods.dev/badge/skills/leochiu-a/elden-ring-github/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.00087 | $0.01057 |
| Opus 5.5 | $0.00035 | $0.00423 |
| Sonnet 5.5 | $0.00017 | $0.00211 |
| Haiku 4.5 | $0.00009 | $0.00106 |
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 2mo 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bump Version
This repo has two version sources that must stay in sync:
package.json— managed by changesets..changeset/config.jsonhas"commit": true, sochangeset versionauto-creates aRELEASING: ...commit.manifest.json— the shipped Chrome-extension version. Not managed by changesets; must be bumped manually.
Step 1: Assess current state
grep '"version"' package.json manifest.json
ls .changeset/*.md # pending changesets (ignore README.md and config.json)
git tag --sort=-v:refname | head -3
Read each pending changeset's frontmatter (major / minor / patch) to know the resulting bump — the highest bump type wins. Report the target version and any pre-existing version mismatch between the two files to the user before proceeding.
Step 2: Run the changeset version bump
Node tooling is often not on PATH in non-interactive shells. Prepend the paths and call the CLI directly:
export PATH="/opt/homebrew/bin:/usr/local/bin:$HOME/Library/pnpm:$PATH"
node node_modules/@changesets/cli/bin.js version
This bumps package.json, rewrites CHANGELOG.md, consumes the changesets, and auto-commits a RELEASING: ... commit.
Note:
git commit --amendon that auto-generated commit is blocked by the permission classifier. Do not try to fold the manifest change into it — use a separate commit (Step 4).
Step 3: Sync manifest.json
Read the new version from package.json, then update manifest.json's "version" field to match (Edit tool).
Step 4: Commit the manifest sync
export PATH="/opt/homebrew/bin:/usr/local/bin:$PATH"
git add manifest.json
git commit -m "chore(release): sync manifest version to <NEW_VERSION>
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>"
Step 5: Tag the release
Tag the manifest-sync commit (where both files reach the new version) with a v-prefixed tag, matching the existing convention (v1.5.0, v2.0.0):
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.
- 2mo ago First seen · 89 lines · 87 tokens per session scan A ea3759c52cc8
bump-version is a skill published in the GitHub repository leochiu-a/elden-ring-github (24 stars, last pushed 3mo ago), licensed MIT. It adds 87 tokens to every session and 1,057 once invoked, about $0.0003 per session on Opus 5.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-09-01.
bump-version compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| bump-versionleochiu-a/elden-ring-github | Skill | 24 | 3mo ago | MIT | A | 87 | Claude Code |
| release-announcementpaperclipai/paperclip | Skill | 111k | yesterday | MIT | A | 42 | Claude Code, Codex |
| releasethedotmack/claude-mem | Skill | 114k | yesterday | Apache-2.0 | A | 13 | Claude Code |
| release-notesphuryn/pm-skills | Skill | 28k | 8d ago | MIT | A | 57 | Claude Code |
| multi-agent-release-managerchromium/chromium | Skill | 25k | yesterday | BSD-3-Clause | A | 27 | Claude Code, Codex |
| pack-submitaeonfun/aeon | Skill | 788 | yesterday | MIT | A | 27 | Claude Code, Codex |
| updater_guidesiddsachar/row-bot | Skill | 1.7k | yesterday | Apache-2.0 | A | 22 | Claude Code, Codex |