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 commands/ofcskn/mobile-automation-plugin/msd-validategit 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.00008 | $0.00119 |
| Opus 5 | $0.00004 | $0.00060 |
| Sonnet 5 | $0.00002 | $0.00024 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
msd-validate 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 2d 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
Run the full validation suite for the specified app without submitting.
Ask: app ID.
Run in sequence, capturing output from each:
node skills/managing-store-metadata/scripts/validate-metadata.js {appId}node skills/managing-app-localizations/scripts/validate-translations.js {appId}node skills/submitting-app-release/scripts/release-checklist.js {appId}
Report pass/fail for each gate with specific failure details. Do not submit anything — validation only.
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.
- 2d ago First seen · 16 lines · 8 tokens per session scan A 714f4285f09d
msd-validate is a command published in the GitHub repository ofcskn/mobile-automation-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 8 tokens to every session and 119 once invoked, about $0.0000 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 commands, from other repositories
release
릴리즈 절차 — 버전 추천부터 릴리즈 PR까지 (changesets, 가이드형).
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.
release-mobilewright
Prepare a mobilewright release by updating CHANGELOG.md with the next patch version.
translate
Translate content into 15 languages while preserving brand voice, citations, and SEO optimization.
release-build
Build release APK/AAB with signing, ProGuard/R8, and optimizations.
add-string
Add a user-facing string/plural to all 16 locales (Android + iOS).