Borrowing it
Nothing to install: this file belongs to korjwl1/toki-monitor. 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/korjwl1/toki-monitor/main/.claude/skills/bump-version/SKILL.mdgit clone --depth 1 https://github.com/korjwl1/toki-monitorWrote 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/korjwl1/toki-monitor/bump-version)<a href="https://agentmods.dev/skills/korjwl1/toki-monitor/bump-version"><img src="https://agentmods.dev/badge/skills/korjwl1/toki-monitor/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/korjwl1/toki-monitor/bump-version"><img src="https://agentmods.dev/badge/skills/korjwl1/toki-monitor/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.00021 | $0.01146 |
| Opus 5.5 | $0.00008 | $0.00458 |
| Sonnet 5.5 | $0.00004 | $0.00229 |
| Haiku 4.5 | $0.00002 | $0.00115 |
Grade C, and why
bump-version scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf build How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bump the version to $ARGUMENTS, build the app, create a GitHub release, and update the Homebrew cask.
If no argument is provided, ask the user what version to bump to.
Step 0 — Release compatibility gate
Before changing a version, run the full test suite and confirm which ecosystem
revisions the release needs. Window/Plan Fit builds require a released toki that
serves toki query windows and WINDOWS. Monitor-settings sync additionally
requires a compatible toki-sync release and protocol tag. The v0.3.0 baseline
is toki v2.3.0, toki-sync v2.2.0, and toki-sync-protocol v1.1.0. Do not publish
the monitor before new required server/protocol capabilities are released.
xcodebuild test -project TokiMonitor.xcodeproj -scheme TokiMonitor \
-destination 'platform=macOS'
Only the three documented timer-driven TokenAggregator skips are expected.
Step 1 — Update version strings
Update the version in both files to the exact same value:
TokiMonitor/Info.plist— the<string>underCFBundleShortVersionStringproject.yml— theCFBundleShortVersionStringvalue
Rules:
- Semver format only (e.g.
0.2.0,1.0.0). Novprefix. - Show a summary of what was changed.
Step 2 — Commit and tag
- Stage the two changed files and create a commit:
chore: bump version to <VERSION> - Create a git tag:
v<VERSION> - Push the commit and tag to origin.
Step 3 — Build the app
xcodebuild -project TokiMonitor.xcodeproj -scheme TokiMonitor -configuration Release -derivedDataPath build clean build
If the build fails, stop and report the error. Do NOT continue.
Step 4 — Package the zip
# Find the .app in the build output
cd build/Build/Products/Release
# Create the release zip
zip -r -y "TokiMonitor-<VERSION>.zip" TokiMonitor.app
Step 5 — Create GitHub release
gh release create "v<VERSION>" \
"build/Build/Products/Release/TokiMonitor-<VERSION>.zip" \
--repo korjwl1/toki-monitor \
--title "v<VERSION>" \
--generate-notes
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 · 126 lines · 21 tokens per session scan C 3032e81b0fe1
bump-version is a skill published in the GitHub repository korjwl1/toki-monitor (23 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 1,146 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
omh-release-cut
This is an OMH release-cut workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
omh-deploy-and-monitor
This is an OMH deploy-and-monitor workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
release-rollback
Plan and execute authorized release promotion or rollback with exact artifact and data compatibility. Use when deploying versions, changing traffic or recovering a bad release; do not equate reversing code with restoring data.