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 skills/leochiu-a/elden-ring-github/bump-versionnpx skills add leochiu-a/elden-ring-github --skill bump-versiongit clone --depth 1 https://github.com/leochiu-a/elden-ring-githubWhat 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.00087 | $0.01057 |
| Opus 5 | $0.00044 | $0.00528 |
| Sonnet 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 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 — 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.
- yesterday 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 1mo ago), licensed MIT. It adds 87 tokens to every session and 1,057 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-09-01.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
release-notes
Draft concise release notes.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
store-update
在 CCX Desktop 发布后下载 Store MSIX 并生成发布公告。用户提到 Store 上架、MSIX、从 GitHub Release 下载 store.msix、发布后同步 Windows Store、从 release 填写商店更新内容时必须使用此技能。该技能会下载最新 GitHub Release 的 amd64/arm64 MSIX，校验 sha256，从 Release body 生成 Store listing releaseNotes 预览，并输出手动上传指引。.