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-initgit 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.00021 | $0.00774 |
| Opus 5 | $0.00010 | $0.00387 |
| Sonnet 5 | $0.00004 | $0.00155 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
msd-init 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize a new app for the automobileapp pipeline.
What to ask the user
- App ID — short slug used for all directories (e.g.
myapp,zenapp). Must be filesystem-safe. Must NOT end with.app— macOS treats any folder ending in.appas an application bundle; App Store tooling will reject uploads from such a path. - Display name — human-readable name shown in stores
- Path to Expo/React Native app — absolute path to the app's root directory
- Platforms — iOS, Android, or both?
- Primary locale — default
en - Additional locales — e.g.
tr,de,fr(comma-separated) - Bundle ID / Package name — e.g.
com.example.myapp
Steps to execute
- Read
.msd/memory/apps.json— if the file does not exist, create it with this default content before proceeding:
This file is gitignored — it stays local to this machine only.{ "_comment": "App registry — managed by /msd-init and msd-* commands. Do not edit manually.", "apps": {}, "preferences": { "appsDirectory": "", "defaultPlatforms": ["ios", "android"], "autoGenerateReleaseNotes": true, "releaseNotesStyle": "friendly", "defaultLocale": "en" } } - Check if appId already exists — if yes, ask to update or cancel
- Create directories:
mkdir -p .msd/config .msd/versions/{appId} .msd/metadata/{appId}/ios/en-US .msd/metadata/{appId}/android/en-US .msd/locales/{appId} .msd/screenshots/{appId} - Copy
.msd/config/.template.config.json→.msd/config/{appId}.config.jsonand fill in values - Create
.msd/versions/{appId}/version.json:{"semver":"1.0.0","ios":{"CFBundleShortVersionString":"1.0.0","CFBundleVersion":"1"},"android":{"versionName":"1.0.0","versionCode":1}} - Read
app.jsonfrom the user's app path and pre-fill metadata where possible (app name →name.txt, etc.) - Create stub metadata files with placeholder text for required fields
- Register in
.msd/memory/apps.json:{ "appId": "{appId}", "displayName": "{displayName}", "path": "{appPath}", "platforms": [...], "locales": [...], "bundleId": {"ios": "{bundleId}", "android": "{androidPkg}"}, "currentVersion": "1.0.0", "firstRelease": {"ios": false, "android": false}, "storeIds": {"ios": null, "android": null}, "addedAt": "{today}" } - Tell user: "App
{appId}registered. Next:/msd-checklist {appId} iosor/msd-checklist {appId} android"
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 · 66 lines · 21 tokens per session scan A b37aba573cc5
msd-init is a command published in the GitHub repository ofcskn/mobile-automation-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 774 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
auto
Intent-classified router, the front door to OrchestKit and the DEFAULT entry point for any goal-shaped request. Classifies a plain-English goal and routes it to the right specialist skill. Routing is never overhead, so use it even when the target skill seems obvious; skip only when already executing inside another…
node-skill
Generate a Claude skill for a ComfyUI custom node pack.
review-android
Guided Android code review workflow through context gathering, Android-specific review, and output.
compose-preview
Generate and verify Compose previews for UI components.
decompile
Decompile an Android APK/XAPK/AAB/DEX/JAR/AAR and analyze its structure.
ios-audit-site
Audit any website for App Store-ready iOS conversion.