msd-release-notes

A release-note generator for mobile apps that creates store-ready updates in every configured language for Android and iOS.

In plain words
What is it for?
Use it to turn a plain-English list of changes into short translated notes, grouped by language in files ready to copy into the store consoles.
Why use it?
It removes the need to write and organise the same version update separately for each language and app store.

Command

Part of the automobileapp plugin — 11 skills, 17 commands, 9 agents shipped together

Install

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.

agentmods
npx agentmods add commands/ofcskn/mobile-automation-plugin/msd-release-notes
Clone the repo
git clone --depth 1 https://github.com/ofcskn/mobile-automation-plugin

Or install automobileapp, the plugin that ships this one along with the rest of its 11 skills, 17 commands, 9 agents.

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 893 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00027 $0.00893
Opus 5 $0.00014 $0.00447
Sonnet 5 $0.00005 $0.00179
Haiku 4.5 $0.00003 $0.00089

Measured 2d ago against content hash dcf1c43c1161, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

commands/msd-release-notes.md · 91 lines

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

  1. Read .msd/memory/apps.json for the app's locale list and bundle ID

  2. Read .msd/versions/{appId}/version.json for the current version

  3. Ask (if not provided): "What changed in this version? Describe in plain English — I'll adapt it per language."

  4. 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)
  5. Show the complete consolidated file contents to the user and ask: "Approve? Or edit any locale?"

  6. 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.")

Read the full file on GitHub · 91 lines

Changes

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.

  1. 2d ago First seen · 91 lines · 27 tokens per session scan A dcf1c43c1161

Subscribe to this mod's changes

msd-release-notes is a command published in the GitHub repository ofcskn/mobile-automation-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 893 once invoked, about $0.0001 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.