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 suntay44/web-to-mobile-magic-plugin --skill mobile-migration-plangit clone --depth 1 https://github.com/suntay44/web-to-mobile-magic-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/suntay44/web-to-mobile-magic-plugin/mobile-migration-plan)<a href="https://agentmods.dev/skills/suntay44/web-to-mobile-magic-plugin/mobile-migration-plan"><img src="https://agentmods.dev/badge/skills/suntay44/web-to-mobile-magic-plugin/mobile-migration-plan/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/suntay44/web-to-mobile-magic-plugin/mobile-migration-plan"><img src="https://agentmods.dev/badge/skills/suntay44/web-to-mobile-magic-plugin/mobile-migration-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00035 | $0.00618 |
| Opus 5 | $0.00017 | $0.00309 |
| Sonnet 5 | $0.00007 | $0.00124 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
mobile-migration-plan 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 today.
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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Migration Plan
Required Input
Use web-to-mobile-audit findings and recommended stack unless evidence changes.
If findings are missing, audit first.
Plan File
Repo/local: docs/web-to-mobile/YYYY-MM-DD-web-to-mobile-plan.md.
URL-only: docs/web-to-mobile/YYYY-MM-DD-ui-ux-spec.md; layout, navigation,
and visual direction only (see references/output-contracts.md).
Use the current local date for a new run. For the current run, update that file in place,
preserving Audit Findings, completed items, and approval history. An audit file marked
Plan Status: Audit complete — planning pending is the same run. Add a numeric
suffix only for a distinct run whose filename collides.
Required Sections
Follow references/plan-template.md in order, including Capabilities & Limits,
Migration Fit Verdict, API Needs, Reusable Code, Rewrite-Required Code, Native
Feature Gaps, Unknowns And Blockers, Implementation Checklist, and Human
Sign-Off Required.
The Migration Fit Verdict chooses one path. Do not force native when a wrapper or PWA suffices. The verdict controls the next phase:
- Expo React Native → approval, then
expo-react-native-build. - Capacitor, PWA/PWABuilder, Stay Web → approval, then explicit web-stack handoff; no Expo build or mobile parity phase.
- Swift/Native → native-team handoff after approval; no bundled implementation.
Read only the detected framework's section in references/framework-migration-notes.md
and relevant packages in references/dependency-substitutions.md for reuse/rewrite
decisions, equivalents, and difficulty. Reuse findings already in context.
In the Route To Mobile Navigation Map, use tabs for primary areas, stacks for details, auth flows for login/signup, modals for focused flows, and explicit deferrals.
The Implementation Checklist needs checkboxes, file paths, source → target
mappings, an observable done condition, verification commands (or Test Plan IDs),
and a confidence label ([from-code], [inferred], [assumption]) per item.
Order by dependencies; identify blocked items and the next unblocked action.
What ships with it
4 files 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.
- today Changed · -19 lines 7566148e8a6e
- 9d ago First seen · 80 lines · 35 tokens per session scan A 1cf2fdf40e62
mobile-migration-plan is a skill published in the GitHub repository suntay44/web-to-mobile-magic-plugin (106 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 618 once invoked, about $0.0002 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-30.
Other skills, from other repositories
orca-emulator-android
Android device and emulator control from inside Orca over adb, with the live device view in Orca's emulator pane. Use when driving an adb-connected emulator or phone on Windows, Linux, or macOS: booting AVDs, taps, swipes, typing, hardware buttons, rotation, app install and launch, runtime permissions, the…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
apple-search-ads
When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT"…
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.