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-scangit 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-scan)<a href="https://agentmods.dev/skills/suntay44/web-to-mobile-magic-plugin/mobile-qa-scan"><img src="https://agentmods.dev/badge/skills/suntay44/web-to-mobile-magic-plugin/mobile-qa-scan/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-scan"><img src="https://agentmods.dev/badge/skills/suntay44/web-to-mobile-magic-plugin/mobile-qa-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 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 36 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 36 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 38 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 53 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.00054 | $0.00670 |
| Opus 5 | $0.00027 | $0.00335 |
| Sonnet 5 | $0.00011 | $0.00134 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
mobile-qa-scan 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile QA Scan
Produce a structured QA report for an existing mobile app without deep source file reads.
Token Rule
Run commands and use the audit script JSON. Do not read source files unless a command fails and the error cannot be diagnosed from its output alone.
Steps
1. Audit script
node <mobile-app-audit-skill-dir>/scripts/mobile-app-audit.mjs <target-path>
Resolve <mobile-app-audit-skill-dir> from the installed sibling
../mobile-app-audit skill directory, not from the user's working directory.
Use the JSON for: framework, screens (implemented/partial/broken counts),
incomplete markers, nav, auth, state, storage, test libraries, build config, and
completion risks.
2. Run commands
Discover commands in this priority order: check scripts in package.json first, then fall back to the tool directly, then check devDependencies for the tool.
- Lint:
npm run lint→eslint .→ skip if eslint not in devDeps. - Typecheck:
npm run typecheck→tsc --noEmit→ skip if no tsconfig. - Tests:
npm test→jest→ skip if no test library detected. - Expo compatibility:
npx expo-doctorandnpx expo install --checkwhen Expo is installed. - Build smoke check:
npm run build→npx expo export→ skip if no Expo dependency.
Record pass/fail and captured output for each — no ✅ without captured output
(see ../mobile-migration-plan/references/output-contracts.md). If a command is
missing, record as "not configured."
3. Write the QA Report
Create docs/mobile-qa/YYYY-MM-DD-qa-report.md with:
- Summary: app name, framework, date.
- Build Health: lint, typecheck, build — ✅ Pass / ⚠️ Warning / ❌ Fail per check.
- Test Coverage: test libraries present, test file count, test run result.
- Structure Overview: screen counts (implemented/partial/broken), nav type, key deps.
- Bundle Size: report
npx expo exportoutput by platform and compare it with a recorded baseline or project budget. If no baseline exists, report the measurement without inventing universal pass/fail thresholds. - Incomplete Markers: TODO/FIXME/placeholder counts by file.
- Risks and Blockers: from audit
completionRisksplus command failures. - Verdict:
Shippable/Needs Work/Blocked— with one-sentence rationale per area and an overall verdict.
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 · 61 lines · 54 tokens per session scan A c18bd3452baf
mobile-qa-scan is a skill published in the GitHub repository suntay44/web-to-mobile-magic-plugin (106 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 670 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
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.
agent-device
Automates Apple-platform apps (iOS, tvOS, macOS), Android devices, and Amazon Vega OS TV apps in Vega Virtual Devices. Use when navigating apps, taking snapshots/screenshots where supported, driving TV remotes, tapping, typing, scrolling, extracting UI info, collecting evidence, or planning agent-device CLI commands.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.
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…