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 web-to-mobilegit 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/web-to-mobile)<a href="https://agentmods.dev/skills/suntay44/web-to-mobile-magic-plugin/web-to-mobile"><img src="https://agentmods.dev/badge/skills/suntay44/web-to-mobile-magic-plugin/web-to-mobile/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/web-to-mobile"><img src="https://agentmods.dev/badge/skills/suntay44/web-to-mobile-magic-plugin/web-to-mobile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 69 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00056 | $0.00686 |
| Opus 5 | $0.00028 | $0.00343 |
| Sonnet 5 | $0.00011 | $0.00137 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
web-to-mobile 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 10d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WebToMobile
One-command orchestrator for turning a website or web app into a mobile app.
The public invocation is:
/web-to-mobile [website_url | github_repo_url | local_path]
In Codex, users can ask: "Use the web-to-mobile skill on [website_url | github_repo_url | local_path]."
Route The Workflow
Use one phase skill at a time:
web-to-mobile-auditinspects the target and records evidence.mobile-migration-plancreatesdocs/web-to-mobile/YYYY-MM-DD-web-to-mobile-plan.mdwith route map, checklist, test plan, acceptance criteria, and approval gate.- Route by the approved Migration Fit Verdict. Expo React Native continues to
expo-react-native-build; Capacitor, PWA/PWABuilder, Stay Web, and Swift/Native receive an explicit implementation handoff because their build phases are not bundled here. - For an Expo build,
mobile-parity-checkverifies design and functional parity against the web source. mobile-qa-releaseverifies the Expo build before completion.
Do not skip directly to build work. Do not generate or edit app code until a plan exists and the user approved it.
Target Classification
Classify the optional argument:
- No argument: use the current workspace as the source web app.
http://orhttps://non-GitHub URL: treat as a live website.https://github.com/<owner>/<repo>: treat as a GitHub repository.- Local path: treat as a local source folder.
For live websites, inspect public pages with available browser/fetch tools. This
is the UI/UX-only tier: you can plan layout, navigation, and visual direction,
but not logic, state, or API behavior. Explain that a faithful code port
requires repository or local source access (see
../mobile-migration-plan/references/output-contracts.md).
For GitHub repositories, clone or inspect the repo only when the environment and permissions allow it. If cloning is not possible, ask the user to provide a local checkout.
For local folders or current workspaces, inspect files directly before advising.
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.
- 10d ago First seen · 75 lines · 56 tokens per session scan A 5ff6e1652851
web-to-mobile is a skill published in the GitHub repository suntay44/web-to-mobile-magic-plugin (106 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 686 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-30.
Other skills, from other repositories
expo-native-ui
Framework (OSS). Build beautiful, native-feeling Expo screens. Covers Apple HIG styling, semantic colors, native controls, SF Symbols, media, visual effects, gradients, storage, and responsive layout. For routing and navigation, use the expo-router skill; for motion and animation, use the expo-animation skill.
expo-web-to-native
Framework (OSS). Migrate an existing web React app to a native iOS/Android app with Expo. Use when the user wants to turn a website into a mobile app, port a Next.js/Vite/CRA React codebase to React Native, reuse web code on native incrementally, or asks how web idioms (the DOM, CSS, React Router, localStorage…
truesheet-usage
Consumer-side guide for integrating @lodev09/react-native-true-sheet into a React Native app. Use this skill whenever the user wants to add, configure, control, or debug a bottom sheet using TrueSheet — including ref-based sheets, named global sheets, web support with TrueSheetProvider/useTrueSheet, React Navigation…
building-ui
Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
use-dom
Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.
react-native-ease-refactor
Scan for Animated/Reanimated code and migrate to EaseView.