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-qa-releasegit 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-qa-release)<a href="https://agentmods.dev/skills/suntay44/web-to-mobile-magic-plugin/mobile-qa-release"><img src="https://agentmods.dev/badge/skills/suntay44/web-to-mobile-magic-plugin/mobile-qa-release/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-qa-release"><img src="https://agentmods.dev/badge/skills/suntay44/web-to-mobile-magic-plugin/mobile-qa-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium MCP Rug Pull · line 34 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 34 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00042 | $0.00696 |
| Opus 5 | $0.00021 | $0.00348 |
| Sonnet 5 | $0.00008 | $0.00139 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
mobile-qa-release 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 9d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile QA Release
Verify before claiming the mobile migration is complete.
Verification Rules
Do not claim completion without fresh evidence. Paste each command, its exit
code, and key output beneath the check — no ✅ without proof (see
../mobile-migration-plan/references/output-contracts.md). Work from the
approved Markdown plan (under docs/web-to-mobile/ or docs/mobile-resume/
depending on the workflow) and the implementation changes. If no plan file
exists, proceed with generic checks, note the absence in the report, and skip
checklist update steps.
Run relevant checks from the plan and repo, such as:
- Dependency install or resolution.
- Lint.
- Typecheck.
- Unit tests.
- Integration or component tests.
- Expo start, export, build, or prebuild smoke check.
- iOS simulator, Android emulator, browser preview, or physical-device smoke test when available.
- Manual checks for navigation, auth, forms, API calls, storage, media, permissions, loading states, and error states.
Performance:
- Run
npx expo-doctor,npx expo install --check, andnpx expo exportfor Expo projects. Compare per-platform JavaScript/assets against the project's recorded baseline or budget; if none exists, record a baseline without inventing a universal threshold. - Observe cold-start time on simulator or device; note if sluggish.
- Spot-check scroll and transition FPS on list screens; note jank.
- Confirm images are appropriately sized and not loading full-resolution web assets.
Accessibility:
- Confirm every interactive element has an accessible name. Native text
children may already provide one; add
accessibilityLabelwhen the visible content does not describe the action (for example, icon-only controls). - Confirm text respects system font scaling (no fixed-height containers that clip scaled text).
- Confirm
accessibilityRoleis set on custom interactive components. - Note any color-only information that may fail contrast requirements.
Responsive Layout:
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.
- 9d ago First seen · 81 lines · 42 tokens per session scan A 14c73291d89d
mobile-qa-release is a skill published in the GitHub repository suntay44/web-to-mobile-magic-plugin (106 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 696 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
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
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.
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.
eas-simulator
EAS service (paid). Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any eas simulator: commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas…
flutter-add-integration-test
Configures Flutter Driver for app interaction and converts MCP actions into permanent integration tests. Use when adding integration testing to a project, exploring UI components via MCP, or automating user flows with the integrationtest package.