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-release-notes)<a href="https://agentmods.dev/commands/ofcskn/mobile-automation-plugin/msd-release-notes"><img src="https://agentmods.dev/badge/commands/ofcskn/mobile-automation-plugin/msd-release-notes/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-release-notes"><img src="https://agentmods.dev/badge/commands/ofcskn/mobile-automation-plugin/msd-release-notes.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.00027 | $0.00893 |
| Opus 5.5 | $0.00011 | $0.00357 |
| Sonnet 5.5 | $0.00005 | $0.00179 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
msd-release-notes 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate release notes for the current version across all configured locales.
Usage
/msd-release-notes {appId} or /msd-release-notes {appId} "Fixed crash on startup, added dark mode"
Output format
All locales are written into one file per platform:
.msd/metadata/{appId}/android/release_notes.txt.msd/metadata/{appId}/ios/release_notes.txt
Each file uses XML locale tags so the user can copy-paste per locale into the store console:
<en-US>
Short release note in English.
</en-US>
<de-DE>
Kurze Versionsnotiz auf Deutsch.
</de-DE>
<tr-TR>
Türkçe kısa sürüm notu.
</tr-TR>
Do NOT create per-locale subfolders for release notes. Store everything in the platform root.
Steps
-
Read
.msd/memory/apps.jsonfor the app's locale list and bundle ID -
Read
.msd/versions/{appId}/version.jsonfor the current version -
Ask (if not provided): "What changed in this version? Describe in plain English — I'll adapt it per language."
-
Draft notes for ALL locales at once:
- Android: max 500 chars total per locale block — keep to 1–2 short sentences
- iOS: max 4000 chars per locale — still keep to 1–2 short sentences for clarity
- Write in each language naturally (not a literal translation)
-
Show the complete consolidated file contents to the user and ask: "Approve? Or edit any locale?"
-
Write the approved content to:
.msd/metadata/{appId}/android/release_notes.txt.msd/metadata/{appId}/ios/release_notes.txt
Locale code mapping (folder code → BCP-47 tag)
| Folder | XML tag |
|---|---|
| en | en-US |
| de | de-DE |
| es | es-ES |
| fr | fr-FR |
| hi | hi-IN |
| ja | ja-JP |
| ko | ko-KR |
| pt | pt-BR |
| tr | tr-TR |
| zh | zh-Hans |
Use the locale codes from .msd/memory/apps.json. Map each to its BCP-47 tag above.
Per-language tone guidance
Adapt for natural expression — do NOT literally translate English:
en-US: direct, friendly ("We fixed a crash and added dark mode")tr-TR: slightly formal ("Uygulama kararlılığı artırıldı, karanlık mod eklendi")de-DE: precise, compound-words preferred ("Absturz behoben, Dunkelmodus hinzugefügt")ja-JP: polite form, short ("クラッシュを修正し、ダークモードを追加しました。")zh-Hans: concise ("修复崩溃,新增深色模式。")ko-KR: polite ending ("충돌 수정 및 다크 모드 추가.")hi-IN: natural Hindi ("क्रैश ठीक किया, डार्क मोड जोड़ा।")fr-FR: smooth French ("Correction d'un plantage et ajout du mode sombre.")es-ES: natural Spanish ("Corrección de bloqueo y modo oscuro añadido.")pt-BR: Brazilian Portuguese ("Correção de falha e modo escuro adicionado.")
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 · 91 lines · 27 tokens per session scan A dcf1c43c1161
msd-release-notes is a command published in the GitHub repository ofcskn/mobile-automation-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 893 once invoked, about $0.0001 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
feat
Kick off tasks creation for a new feature (4-item interview before invoking pm-agent; an epic-sized requirement routes to phased decomposition, a feature already built on one platform routes to cross-platform parity, a change that touches no endpoint routes to client-only).
app-store-audit
Run an enterprise pre submission compliance audit on an iOS or Android app against Apple App Store and Google Play rejection rules. Pass a project path or run from the project root.
feature-build
Build a complete mobile feature from description to running code with E2E tests. Orchestrates 6 phases - planning, implementation, testing, build-fix, quality gate, and verification. Auto-detects platform.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.