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-parity-checkgit 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-parity-check)<a href="https://agentmods.dev/skills/suntay44/web-to-mobile-magic-plugin/mobile-parity-check"><img src="https://agentmods.dev/badge/skills/suntay44/web-to-mobile-magic-plugin/mobile-parity-check/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-parity-check"><img src="https://agentmods.dev/badge/skills/suntay44/web-to-mobile-magic-plugin/mobile-parity-check.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.00045 | $0.00415 |
| Opus 5 | $0.00023 | $0.00208 |
| Sonnet 5 | $0.00009 | $0.00083 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
mobile-parity-check 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.
What it actually says
Mobile Parity Check
Verify that the mobile implementation faithfully matches the web source before QA.
Required Input
Use the approved plan under docs/web-to-mobile/ — specifically the Route To Mobile Navigation Map, Reusable Code, and Acceptance Criteria sections. If no plan exists, stop and return to mobile-migration-plan.
Functional Parity
For each route in the Route To Mobile Navigation Map:
- Confirm the mapped mobile screen exists and is implemented.
- Confirm all interactions from the web route (forms, buttons, links, data display) are present in the mobile screen.
- Note any web feature that was deferred — it must appear in the plan as an explicit deferral, not a silent omission.
Design Parity
Check what the agent can verify in code:
- Colors: confirm design tokens or hardcoded values match the web source palette.
- Typography: confirm font family, size scale, and weight usage aligns with the web source.
- Spacing and layout: confirm component hierarchy and padding constants are consistent.
- Icons and assets: confirm correct assets are used, not placeholders.
Flag deviations with the specific file and line where the mismatch occurs.
Human Review Required
Mark the following for explicit human visual sign-off — the agent cannot verify these in code:
- Pixel-level layout accuracy on device.
- Animation and transition feel.
- Brand color rendering on screen.
- Accessibility contrast ratios in the rendered UI.
See Human Sign-Off Required in
../mobile-migration-plan/references/output-contracts.md.
Plan Update
Add a "Parity Review" section to the plan listing: agent-verified items, agent-flagged deviations, and items requiring human visual sign-off.
Handoff
End by handing off to mobile-qa-release.
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 · 53 lines · 45 tokens per session scan A dad1869e577e
mobile-parity-check is a skill published in the GitHub repository suntay44/web-to-mobile-magic-plugin (106 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 415 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
animate-expo
Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and…
leanback-to-compose-tv-migration
Provides instructions and architectural patterns for migrating Android TV applications from legacy Leanback UI Toolkit, Android Views, or Support Fragments to Jetpack Compose for TV (androidx.tv). Use this skill for Leanback to Compose migrations, including browse screen, settings screen, authentication screen, login…
maui-data-binding
Guidance for .NET MAUI XAML and C# data bindings — compiled bindings, INotifyPropertyChanged / ObservableObject, value converters, binding modes, multi-binding, relative bindings, fallbacks, and MVVM best practices. USE FOR: setting up compiled bindings with x:DataType, implementing INotifyPropertyChanged or…
migrate-xml-views-to-jetpack-compose
Provides a structured workflow for migrating an Android XML View to Jetpack Compose. This skill details the step-by-step process, from planning and dependency setup, to theming and layout migration, validation and XML cleanup. Use this skill when you need to migrate an XML View to Jetpack Compose in an Android…
web-haptics
Add haptic feedback to web apps using the web-haptics library. Use when building mobile-facing UIs that need tactile feedback on buttons, toggles, forms, pickers, and other interactive elements.
axiom-swiftui
Use when building, fixing, or improving ANY SwiftUI UI — views, navigation, layout, animations, performance, architecture, gestures, debugging, iOS 26 features.