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 skills add ofcskn/mobile-automation-plugin --skill managing-app-registrygit 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/skills/ofcskn/mobile-automation-plugin/managing-app-registry)<a href="https://agentmods.dev/skills/ofcskn/mobile-automation-plugin/managing-app-registry"><img src="https://agentmods.dev/badge/skills/ofcskn/mobile-automation-plugin/managing-app-registry/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.
<a href="https://agentmods.dev/skills/ofcskn/mobile-automation-plugin/managing-app-registry"><img src="https://agentmods.dev/badge/skills/ofcskn/mobile-automation-plugin/managing-app-registry.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00070 | $0.00458 |
| Opus 5 | $0.00035 | $0.00229 |
| Sonnet 5 | $0.00014 | $0.00092 |
| Haiku 4.5 | $0.00007 | $0.00046 |
Grade A, and why
managing-app-registry 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 8d 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
Managing the App Registry
Registry file
.msd/memory/apps.json — single source of truth for all registered apps.
App record schema
{
"appId": "myapp",
"displayName": "My App",
"path": "/path/to/your/expo/app",
"platforms": ["ios", "android"],
"locales": ["en", "tr", "de"],
"bundleId": {
"ios": "com.example.myapp",
"android": "com.example.myapp"
},
"currentVersion": "1.0.0",
"firstRelease": {
"ios": false,
"android": false
},
"storeIds": {
"ios": null,
"android": null
},
"addedAt": "2026-06-23"
}
When to update the registry
- After
/msd-init: create new app record - After first submission completes: set
firstRelease.iosorfirstRelease.androidtotrue - After version bump: update
currentVersion - After locale added: update
locales[]
Reading the registry
Before any release operation, check:
- Is the app registered? If not, run
/msd-init {appId}first. - Is
firstRelease.ios/androidtrue? If not, use the First Release checklist. - What locales are registered? Validate metadata exists for all of them.
App discovery
To find all Expo apps in a directory, look for app.json or app.config.ts files:
find /path/to/projects -name "app.json" -maxdepth 3 | grep -v node_modules
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 62 lines · 70 tokens per session scan A af6fd6308ea5
managing-app-registry is a skill published in the GitHub repository ofcskn/mobile-automation-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 70 tokens to every session and 458 once invoked, about $0.0003 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 skills, from other repositories
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
app-store-preflight-compliance
Pre-submission compliance scanner workflow for Apple App Store apps. Use when reviewing iOS, macOS, tvOS, watchOS, or visionOS projects (Swift, Objective-C, React Native, Expo) for App Store rejection risks, submission readiness, privacy compliance, or guideline violations.
uniwind
Uniwind — Tailwind CSS v4 styling for React Native. Use when adding, building, or debugging components in a React Native project that uses Uniwind classNames. Covers setup, Metro config, global.css, theming, className props, accent- color props, platform/data/state/responsive variants, CSS variables, custom utilities…
e2e-testing
AI-powered E2E testing for any app — Flutter, React Native, iOS, Android, Electron, Tauri, KMP, .NET MAUI. Connects via MCP to running apps so the agent can take screenshots, tap elements, enter text, scroll, inspect UI trees, and verify state with natural language. Use when the user wants to test an app's UI…
Appium Mobile Testing
Mobile application testing skill using Appium for iOS and Android, covering device capabilities, selectors, gestures, and cross-platform testing strategies.