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-checklistgit 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-checklist)<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="Measured on agentmods" 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 | $0.00027 | $0.00481 |
| Opus 5 | $0.00014 | $0.00241 |
| Sonnet 5 | $0.00005 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
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 4d 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 interactive First Release checklist for a platform.
Usage
/msd-checklist {appId} ios or /msd-checklist {appId} android
Steps
-
Read
.msd/memory/apps.json— check iffirstRelease.{platform}is alreadytrue- If
true: say "First release already marked complete. Use the standard release pipeline instead." - If
false: proceed
- If
-
Load the checklist:
- iOS:
docs/apple-store-checklist.md - Android:
docs/play-store-checklist.md
- iOS:
-
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)"
-
Track completed steps in the conversation. Do NOT re-run steps the user already confirmed.
-
When all Part 1 steps complete:
- Update
.msd/memory/apps.json: setfirstRelease.{platform} = true - Say: "🎉 First release pipeline complete for {platform}. Future releases use the automated pipeline."
- Update
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.
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.
- 4d ago First seen · 44 lines · 27 tokens per session scan A a17f012656c2
msd-checklist 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 481 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.
Other commands, from other repositories
mobile-verify
Run automated verification loops with pass@k metrics for mobile testing. Executes tests multiple times to detect flakiness.
android-build
Build Android project with Gradle, fix errors, generate APK/AAB. Invokes android-build-resolver for issues.
decompile
Decompile an Android APK/XAPK/AAB/DEX/JAR/AAR and analyze its structure.
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.
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).
ios-site-app
Turn any website or web app into an iOS app plan and build path.