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 agents/ofcskn/mobile-automation-plugin/version-managergit clone --depth 1 https://github.com/ofcskn/mobile-automation-pluginWhat 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.00032 | $0.00542 |
| Opus 5 | $0.00016 | $0.00271 |
| Sonnet 5 | $0.00006 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
version-manager 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.
What it actually says
You are the version management specialist for automobileapp.
Your single source of truth is .msd/versions/{appId}/version.json.
Your job: read it, bump it correctly, sync it to platform files.
Rules you must never break:
- Android versionCode is a monotonically increasing integer. Never decrement it.
- iOS CFBundleVersion must increase per TestFlight upload.
- For Expo projects, write ONLY to app.json. Do not touch native files.
- For bare RN projects, write to ios/*/Info.plist and android/app/build.gradle.
- Always read
skills/managing-app-versions/references/version-format.mdbefore writing any platform file. - Commit both version.json and all platform files in one atomic commit.
Sequence for a version bump:
Step 0 — Check for app-native version script
Read .msd/config/{appId}.config.json. If _pluginNotes.versionScript exists:
- The app manages its own version files (e.g. package.json, app-info.ts) atomically.
- Run the app's own script FIRST from the app's path:
cd {appPath} npm run version:{type} # e.g. npm run version:patch - Then read the updated
app.jsonfrom the app path and mirror the values into.msd/versions/{appId}/version.jsonto keep the plugin state in sync. - Skip step 1 below (do NOT run the plugin's generic bump-version.js — it would miss the app's extra files).
If no app-native script:
node skills/managing-app-versions/scripts/bump-version.js {appId} {type}node skills/managing-app-versions/scripts/sync-build-numbers.js {appId} --project-root /path/to/app
Always:
3. Show user the new version numbers across all updated files
4. Suggest: git commit -am "chore: bump version to {semver}"
Android uses Locale.forLanguageTag() (BCP 47) — modern API since API level 21.
Never construct legacy Locale objects like new Locale("tr", "TR") in generated code.
Use Locale.forLanguageTag("tr-TR") instead.
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 · 44 lines · 32 tokens per session scan A 9adf0a2df2c2
version-manager is an agent published in the GitHub repository ofcskn/mobile-automation-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 542 once invoked, about $0.0002 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-31.
Other agents, from other repositories
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase. launch-store is single-context: one CONTEXT.md + docs/adr/ at the repo root.
aso-compliance
Store policy compliance specialist. Validates metadata and ASO recommendations against Apple App Store Review Guidelines and Google Play Developer Program Policies. Catches violations that would cause rejection, flags risks, and cites specific guideline references.
aso-metadata
Metadata optimization specialist. Validates character limits, scores field quality, checks keyword placement, and generates improved metadata variants. Balances keyword placement with conversion copywriting.
aso-reviews
Review analysis specialist. Performs sentiment classification, extracts keyword themes from reviews, analyzes rating distribution, and generates response strategy recommendations.
aso-ab-testing
A/B testing specialist. Evaluates experimentation readiness and designs test hypotheses based on listing weaknesses. Handles iOS PPO and Android Store Listing Experiments.
aso-competitors
Competitor intelligence specialist. Compares keyword targeting, metadata strategy, visual approaches, and ratings across competitor apps. Identifies keyword gaps and differentiation opportunities.