.NET MAUI is a C# and XAML framework for building native mobile and desktop applications from one shared codebase. Developers use it to create apps for Android, iOS, iPadOS, macOS, and Windows. The catalogue entries provide skills, instructions, and agents for working with .NET MAUI.
Borrowing it
Nothing to install: this file belongs to dotnet/maui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dotnet/maui/main/.github/instructions/uitests.instructions.mdgit clone --depth 1 https://github.com/dotnet/mauiWrote 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/instructions/dotnet/maui/uitests)<a href="https://agentmods.dev/instructions/dotnet/maui/uitests"><img src="https://agentmods.dev/badge/instructions/dotnet/maui/uitests/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/instructions/dotnet/maui/uitests"><img src="https://agentmods.dev/badge/instructions/dotnet/maui/uitests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.07402 | $0.07402 |
| Opus 5.5 | $0.02961 | $0.02961 |
| Sonnet 5.5 | $0.01480 | $0.01480 |
| Haiku 4.5 | $0.00740 | $0.00740 |
Grade A, and why
maui uitests.instructions.md 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 3d 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 — 782 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Testing Guidelines for .NET MAUI
Overview
This document provides specific guidance for GitHub Copilot when writing UI tests for the .NET MAUI repository.
Critical Principle: UI tests should run on all applicable platforms (iOS, Android, Windows, MacCatalyst) by default unless there is a specific technical limitation.
UI Test Structure
Two-Project Requirement
CRITICAL: Every UI test requires code in TWO separate projects:
-
HostApp UI Test Page (
src/Controls/tests/TestCases.HostApp/Issues/)- Create the actual UI page that demonstrates the feature or reproduces the issue
- Prefer C# only (
.csfile) unless testing XAML-specific features (bindings, templates, styles) - Add
AutomationIdattributes on interactive controls for test automation - Follow naming convention:
IssueXXXXX.cs(C# only) orIssueXXXXX.xaml+IssueXXXXX.xaml.cs(when XAML required) - XXXXX should correspond to a GitHub issue number when applicable
- Ensure the UI provides clear visual feedback for the behavior being tested
- Class must include
[Issue()]attribute with tracker, number, description, and platform
-
NUnit Test Implementation (
src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/)- Create corresponding Appium-based NUnit tests that inherit from
_IssuesUITest - Use the
AutomationIdvalues to locate and interact with UI elements - Follow naming convention:
IssueXXXXX.cs(matches the HostApp page file) - Include one functional
[Category(UITestCategories.XYZ)]attribute per test - CollectionView tests use
[ShardedTestCategory(UITestCategories.CollectionView, shard: N)], which exposes both theCollectionViewumbrella and one numbered CI shard category - Shell tests use
[ShardedTestCategory(UITestCategories.Shell, shard: N)]; CI usesShell1andShell2on Android, iOS, Windows, and MacCatalyst, while local umbrella runs continue to useShell - Omitted
sharddefaults to shard 1 so a new test cannot silently cease running; the rebalancing skill assigns the durable shard - Put
ShardedTestCategoryon each test method; never put it on the class - A fixture split across shards must initialize every shard in
FixtureSetup; never use anOrder(1)test as setup for later tests - Dedicated stages using
testConfigurationArgs(for exampleios_ui_tests_mono_cv1) are separate configuration coverage and are not ordinary category-matrix shard entries - Test should validate expected behavior through UI interactions and assertions
- Create corresponding Appium-based NUnit tests that inherit from
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.
- 3d ago Changed · +1 lines · +55 tokens per session 9e37e7fba2c6
- 1mo ago Changed · +5 lines · +175 tokens per session f399e4e5f936
- 1mo ago First seen · 776 lines · 7,172 tokens per session scan A 957d718449fb
maui uitests.instructions.md is an instructions file published in the GitHub repository dotnet/maui (23,322 stars, last pushed today), licensed MIT. It adds 7,402 tokens to every session, about $0.0296 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).