agentmods.dev

msd-checklist

msd-checklist is a command for Claude Code from ofcskn/mobile-automation-plugin. It costs 27 tokens per session (481 once invoked), scanned A, original, MIT.

An interactive checklist for releasing an app to Apple’s App Store or Google Play. It separates automated, AI-assisted, manual, and waiting steps.

In plain words
What is it for?
For guiding an iOS or Android app through its first store release using an app ID and platform.
Why use it?
It keeps release requirements in one place and records completed steps, reducing the chance of skipping part of the store submission process.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

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

not rated 2repo 4mo ago A scan 27 tokens original MIT

Good fit For guiding an iOS or Android app through its first store release using an app ID and platform.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ofcskn/mobile-automation-plugin/msd-checklist
View source ↗ ofcskn/mobile-automation-plugin
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.

Clone the repo
git clone --depth 1 https://github.com/ofcskn/mobile-automation-plugin

Made for: Claude Code.

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

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

agentmods badge for msd-checklist

README.md
[![agentmods](https://agentmods.dev/badge/commands/ofcskn/mobile-automation-plugin/msd-checklist/github.svg)](https://agentmods.dev/commands/ofcskn/mobile-automation-plugin/msd-checklist)
Your own site
<a href="https://agentmods.dev/commands/ofcskn/mobile-automation-plugin/msd-checklist"><img src="https://agentmods.dev/badge/commands/ofcskn/mobile-automation-plugin/msd-checklist/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.

agentmods 80×15 button for msd-checklist

Your own site · 80×15
<a href="https://agentmods.dev/commands/ofcskn/mobile-automation-plugin/msd-checklist"><img src="https://agentmods.dev/badge/commands/ofcskn/mobile-automation-plugin/msd-checklist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 481 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00027 $0.00481
Opus 5.5 $0.00011 $0.00192
Sonnet 5.5 $0.00005 $0.00096
Haiku 4.5 $0.00003 $0.00048

Measured 1mo ago against content hash a17f012656c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

commands/msd-checklist.md · 44 lines

What it actually says

Run the interactive First Release checklist for a platform.

Usage

/msd-checklist {appId} ios or /msd-checklist {appId} android

Steps

  1. Read .msd/memory/apps.json — check if firstRelease.{platform} is already true

    • If true: say "First release already marked complete. Use the standard release pipeline instead."
    • If false: proceed

  2. Load the checklist:

    • iOS: docs/apple-store-checklist.md
    • Android: docs/play-store-checklist.md

  3. Walk through Part 1 step by step:

    • 🟢 AUTOMATED steps: Run them immediately, show output, mark ✅ done
    • 🟡 AI-ASSISTED steps: Generate the content (metadata, release notes brief), show it to user, ask "Approve this? (yes/edit/skip)"
    • 🔴 MANUAL steps: Show the step details, explain exactly what to do and where, then ask "Have you completed this step? (yes/skip)"
    • ⏳ WAITING steps: Note what to wait for, ask "Continue when ready (press Enter)"

  4. Track completed steps in the conversation. Do NOT re-run steps the user already confirmed.

  5. When all Part 1 steps complete:

    • Update .msd/memory/apps.json: set firstRelease.{platform} = true
    • Say: "🎉 First release pipeline complete for {platform}. Future releases use the automated pipeline."

Rules

  • Never skip a 🔴 MANUAL step — these have real consequences (missing privacy labels blocks submission)
  • For 🟡 AI-ASSISTED steps, always show the generated content BEFORE asking for approval
  • Let the user skip optional steps (screenshots for iPad, tablet screenshots for Play)
  • After a user says "yes" to a manual step, trust them — don't ask again

Quick recovery

If the user interrupted mid-checklist, ask: "Where did you leave off? (step number or description)" Then resume from that step.

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. 1mo ago First seen · 44 lines · 27 tokens per session scan A a17f012656c2

Subscribe to this mod's changes

msd-checklist is a command published in the GitHub repository ofcskn/mobile-automation-plugin (2 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 481 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.

Claude CodeGit and workflowMobileReleasesandroidapp-storeautomationclaude-pluginexpo
Related

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.

yonatangross/orchestkit · 62 tokens

ship

Open a pull request for the current branch, drive it green, and merge it.

Cavalry-Collective/visual-stack · 16 tokens

release

Cut a Major.Minor release from the Increment.

nunoamorim99/agile-ledger · 9 tokens

changelog

Export user-facing release notes from the version history (derived, never edits the ledger).

nunoamorim99/agile-ledger · 17 tokens

moodle-bump-version

You will bump the Moodle plugin version and wire the upgrade step.

SaadRahman01/claude-moodle-dev · 0 tokens

launch

Prepare a release by validating the install surface.

noah-sheldon/ai-dev-kit · 11 tokens