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 maui-ui-patternsgit 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/maui-ui-patterns)<a href="https://agentmods.dev/skills/dotnet/maui-labs/maui-ui-patterns"><img src="https://agentmods.dev/badge/skills/dotnet/maui-labs/maui-ui-patterns/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/dotnet/maui-labs/maui-ui-patterns"><img src="https://agentmods.dev/badge/skills/dotnet/maui-labs/maui-ui-patterns.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.00082 | $0.01112 |
| Opus 5.5 | $0.00033 | $0.00445 |
| Sonnet 5.5 | $0.00016 | $0.00222 |
| Haiku 4.5 | $0.00008 | $0.00111 |
Grade A, and why
maui-ui-patterns 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 1mo 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MAUI UI Patterns
Use this skill when creating or reshaping a MAUI page or reusable component. Prefer readable layouts, shared resources, stable automation hooks, and explicit UI states over coordinate-based or screenshot-only UI.
Workflow
- Inspect the existing UI style: XAML, C# Markup, MauiReactor, or Blazor Hybrid. If the requested page/component cannot be found but the user asked for a UI pattern, still provide a self-contained snippet or create the requested file at a sensible path instead of stopping with only a clarification request.
- Choose layout primitives based on content:
Gridfor structured forms and dashboards.FlexLayoutfor wrapping content and responsive chip/card layouts.VerticalStackLayout/HorizontalStackLayoutfor simple linear groups.CollectionViewfor repeated data; avoid wrapping it inScrollView.
- Move repeated colors, spacing, and text styles into resources.
- Add
AutomationIdto important interactive elements. - Add loading, empty, error, and success states for data-driven screens.
For
CollectionViewloading/empty-state requests, show a visible loading element such asActivityIndicator, aCollectionView.EmptyView, and stableAutomationIdvalues for loading/list/empty elements. - Add basic accessibility hooks while building the UI; route deeper audits to
maui-accessibility. - Verify with build plus DevFlow tree/screenshot when available.
Layout Guardrails
| Avoid | Prefer |
|---|---|
| Absolute coordinates for normal app UI | Grid, FlexLayout, and adaptive resources |
Nested ScrollView around CollectionView |
CollectionView scrolling directly |
Fixed HeightRequest to force list scrolling |
Star-sized Grid row so the list receives remaining space |
| Repeated inline colors/margins everywhere | ResourceDictionary styles and spacing resources |
| Text-only UI automation | Stable AutomationId values |
| One giant page without states | Loading, empty, error, and content states |
BindableLayout for long or incremental lists |
CollectionView virtualization and incremental loading |
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.
- 1mo ago Changed · -48 tokens per session d48c60c5353e
- 1mo ago First seen · 117 lines · 130 tokens per session scan A bce4771e6b35
maui-ui-patterns is a skill published in the GitHub repository dotnet/maui-labs (229 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 1,112 once invoked, about $0.0003 per session on Opus 5.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-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-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.
argent-native-profiler
Native profiling for CPU hotspots, UI hangs, memory issues. iOS via xctrace; Android via Perfetto. Use when diagnosing native-level performance issues.
argent-react-native-app-workflow
Step-by-step workflows for developing or debugging React Native apps on iOS simulator or Android emulator. Use when starting the app, debugging Metro, fixing builds, diagnosing runtime errors, or running tests.
symbolication-setup
Configure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or source maps (React Native).
network-tracing
Instrument API requests with spans and distributed tracing. Use when tracking request latency, correlating client-backend traces, or debugging API issues.