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.
git clone --depth 1 https://github.com/ofcskn/mobile-automation-pluginWrote 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/commands/ofcskn/mobile-automation-plugin/msd-bump)<a href="https://agentmods.dev/commands/ofcskn/mobile-automation-plugin/msd-bump"><img src="https://agentmods.dev/badge/commands/ofcskn/mobile-automation-plugin/msd-bump/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/commands/ofcskn/mobile-automation-plugin/msd-bump"><img src="https://agentmods.dev/badge/commands/ofcskn/mobile-automation-plugin/msd-bump.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.00011 | $0.00269 |
| Opus 5.5 | $0.00004 | $0.00108 |
| Sonnet 5.5 | $0.00002 | $0.00054 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
msd-bump 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 1mo 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.
What it actually says
Bump the version for the specified app.
Ask: app ID, bump type (patch / minor / major / build), and optionally platform (ios / android / both — default: both).
Usage examples:
node bump-version.js {appId} patch— bump both platformsnode bump-version.js {appId} minor ios— bump iOS onlynode bump-version.js {appId} patch android— bump Android onlynode bump-version.js {appId} major both— explicit both
Steps:
- Show current version:
cat .msd/versions/{appId}/version.json - Run:
node skills/managing-app-versions/scripts/bump-version.js {appId} {bumpType} [{platform}] - Run:
node skills/managing-app-versions/scripts/sync-build-numbers.js {appId} --project-root {appRoot} - Show the new version numbers (semver, iOS build, Android versionCode)
- Suggest commit message:
chore: bump version to {semver} (build {build})
If the user doesn't know the app project root, default to current working directory.
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.
- 1mo ago First seen · 23 lines · 11 tokens per session scan A cefb05d9d380
msd-bump is a command published in the GitHub repository ofcskn/mobile-automation-plugin (2 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 269 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
ship
Open a pull request for the current branch, drive it green, and merge it.
release
Cut a Major.Minor release from the Increment.
changelog
Export user-facing release notes from the version history (derived, never edits the ledger).
moodle-bump-version
You will bump the Moodle plugin version and wire the upgrade step.
launch
Prepare a release by validating the install surface.