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-buildgit 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-build)<a href="https://agentmods.dev/commands/ofcskn/mobile-automation-plugin/msd-build"><img src="https://agentmods.dev/badge/commands/ofcskn/mobile-automation-plugin/msd-build.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.01046 |
| Opus 5 | $0.00014 | $0.00523 |
| Sonnet 5 | $0.00005 | $0.00209 |
| Haiku 4.5 | $0.00003 | $0.00105 |
Grade A, and why
msd-build 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build the app for the specified profile. Local build is the default — it uses your machine's Xcode/Android Studio, skips the EAS cloud queue, and produces a binary you can submit immediately with --path.
Usage
/automobileapp:msd-build {appId} [development|preview|production] [ios|android|all]
Defaults: production, all platforms.
Step 1 — Ask build mode
"Build locally (uses your Xcode/Android Studio, no cloud queue) or via EAS cloud?
- Local (default) — no build minutes used, no queue wait, binary stays on your machine
- Cloud — EAS manages signing and environment, binary stored in EAS"
If the user doesn't specify, use local.
Step 2 — Pre-build checks
# Read app path
cat .msd/memory/apps.json | node -e "const d=JSON.parse(require('fs').readFileSync('/dev/stdin','utf8')); console.log(d.apps?.find(a=>a.id==='{appId}')?.path || 'not found')"
# Confirm eas.json exists in app root
ls {appPath}/eas.json || echo "❌ eas.json missing — run: cd {appPath} && eas build:configure"
# For production: run pre-flight checklist first
node skills/submitting-app-release/scripts/release-checklist.js {appId}
Step 3a — Local build (recommended)
iOS local
Requirements: Xcode 15+, valid distribution certificate and provisioning profile (EAS manages these — run eas credentials if missing).
cd {appPath}
# Production store build
eas build --local --platform ios --profile production
# Output: ./build-XXXXXXXXXX.ipa (in {appPath})
# Find the output binary
IOS_BUILD=$(find . -maxdepth 2 -name "*.ipa" -newer eas.json | sort -t_ -k2 -n | tail -1)
echo "iOS binary: $IOS_BUILD"
Save $IOS_BUILD path — it is passed to eas submit --path in the next step.
Android local
Requirements: Android Studio, Java 17+, ANDROID_HOME set.
cd {appPath}
# Production AAB (required for Play Store)
eas build --local --platform android --profile production
# Output: ./build-XXXXXXXXXX.aab
# Find the output binary
ANDROID_BUILD=$(find . -maxdepth 2 -name "*.aab" -newer eas.json | sort -t_ -k2 -n | tail -1)
echo "Android binary: $ANDROID_BUILD"
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 · 139 lines · 27 tokens per session scan A ea91392443de
msd-build 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 1,046 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.
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).
deploy
Шаг 6 — GitHub-репозиторий + Vercel-деплой + свой домен. Боевой URL.
ios-site-app
Turn any website or web app into an iOS app plan and build path.
ios-grade
Grade iOS implementation plus App Store readiness and emit PASS/BLOCK.