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 dotnet/maui-labs --skill xamarin-forms-migrationgit clone --depth 1 https://github.com/dotnet/maui-labsWrote 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/dotnet/maui-labs/xamarin-forms-migration)<a href="https://agentmods.dev/skills/dotnet/maui-labs/xamarin-forms-migration"><img src="https://agentmods.dev/badge/skills/dotnet/maui-labs/xamarin-forms-migration.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Rogue Agent · line 126 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00075 | $0.01586 |
| Opus 5 | $0.00037 | $0.00793 |
| Sonnet 5 | $0.00015 | $0.00317 |
| Haiku 4.5 | $0.00007 | $0.00159 |
Grade A, and why
xamarin-forms-migration 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 4d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Xamarin.Forms Migration
Use this skill to move a Xamarin.Forms app to .NET MAUI without blindly copying obsolete patterns. Treat migration as an audit and phased rebuild on a fresh MAUI project unless the user explicitly needs a small tactical port.
Response Checklist
- Call out the migration audit first (
DependencyService,MessagingCenter, custom renderers/effects, permissions, and platform capabilities). - Prefer a fresh MAUI project workflow and
MauiProgram.csDI setup. - Explicitly classify renderer replacements into mapper customization, custom handler, platform service, or slim binding.
Migration Tooling
Before migrating manually, check whether the .NET Upgrade Assistant can cover the mechanical parts of the app:
dotnet tool install -g upgrade-assistant
upgrade-assistant upgrade <your-solution>.sln
Upgrade Assistant can help with project conversion and namespace/API rewrites.
Use this skill for decisions tooling cannot safely automate: renderer
classification, DependencyService lifetimes, MessagingCenter replacement,
platform capability parity, and validation planning.
Migration Workflow
- Inventory the current app:
- Xamarin.Forms version, target platforms, platform projects, NuGet packages,
renderers, effects,
DependencyService,MessagingCenter, and native SDKs. - App startup, navigation, resource dictionaries, images/fonts, and platform entitlements/permissions.
- Xamarin.Forms version, target platforms, platform projects, NuGet packages,
renderers, effects,
- Create a new .NET MAUI project or solution structure that matches the target app shape. Prefer this over editing the Xamarin.Forms project in place.
- Move shared code first: models, services, view models, converters, resources, and XAML. Keep platform code out until shared code builds.
- Update namespaces and APIs using
maui-current-apis; do not introduce newXamarin.FormsorXamarin.Essentialsreferences. - Migrate app startup to
MauiProgram.cs,CreateMauiApp, DI registration, fonts, handlers, lifecycle events, and platform services. - Migrate UI and navigation incrementally. Keep Shell route names, modal flows, and deep-link behavior explicit.
- Plan custom renderer/effect replacements:
- simple native property tweak -> handler mapper customization;
- reusable custom control -> custom handler;
- non-visual platform API -> platform service via DI;
- third-party native SDK surface -> slim binding.
- Validate each migrated slice with build, platform launch, and accessibility or performance checks for changed UI.
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.
- 4d ago Changed · -27 tokens per session e6047e87b29e
- 8d ago First seen · 153 lines · 102 tokens per session scan A b3fad97b3664
xamarin-forms-migration is a skill published in the GitHub repository dotnet/maui-labs (213 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 1,586 once invoked, about $0.0004 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
argent-device-interact
Interact with an iOS simulator, Android emulator, or Chromium (CDP) app using argent MCP tools. Use when tapping UI elements, performing gestures, scrolling/swiping, typing text, pressing hardware buttons, launching apps, opening URLs, taking screenshots, waiting for an element to appear or disappear, or checking…
argent-metro-debugger
Debug a JS runtime via CDP using argent debugger tools. Primary path is React Native via Metro (iOS / Android / Vega); a subset of the tools (debugger-connect, debugger-status, debugger-evaluate, debugger-log-registry) also drive a Chromium (CDP) app's renderer (an Electron app, or any Chromium browser exposing CDP)…
argent-settings-permissions
Grant, deny, or reset an app's runtime permissions (camera, microphone, photos, contacts, notifications, calendar, location, location-always, media-library, motion, reminders) on an iOS simulator or Android device using the argent settings-permissions tool - without navigating the system Settings UI. Use when the…
argent-react-native-optimization
Optimizes a React Native app by profiling first to find real bottlenecks, then sweeping for mechanical issues. Entry-point for all performance work. Use when the app feels slow, user asks to optimize, fix re-renders, reduce jank, or improve startup. Delegates to argent-react-native-profiler for measurement.
mobile-automation
Control Android and iOS devices, emulators and simulators — launch apps, tap, swipe, type, take screenshots, read the accessibility tree. Use when a task involves a mobile device or app, mobile UI testing, or reproducing a bug on a phone.
argent-react-native-profiler
Profile a React Native Hermes app to measure re-render and CPU performance using argent profiler tools. Use when optimizing for performance, measuring before/after a fix, spotting slow components, diagnosing re-renders, checking CPU hotspots, or producing a ranked issue report.