maui: Instructions file for GitHub Copilot

.github/instructions/xaml-unittests.instructions.md

maui xaml-unittests.instructions.md is an instructions file for GitHub Copilot from dotnet/maui. It costs 1,149 tokens per session, scanned A, original, MIT.

A set of guidelines for unit tests of XAML, the markup language used to describe .NET MAUI user interfaces.

In plain words
What is it for?
Use it to add issue-specific XAML tests, verify that pages load, and assert properties or behavior in the Controls.Xaml.UnitTests project.
Why use it?
It keeps XAML tests organized and checks that pages can be created correctly across the supported XAML loading methods.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is dotnet/maui's own configuration. It tells GitHub Copilot how to work on maui itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything maui configures →

About the project

.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.

dotnet/maui · 23,319 stars · on GitHub · dot.net

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/dotnet/maui/main/.github/instructions/xaml-unittests.instructions.md
Clone the repo
git clone --depth 1 https://github.com/dotnet/maui

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for maui xaml-unittests.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/dotnet/maui/xaml-unittests.svg)](https://agentmods.dev/instructions/dotnet/maui/xaml-unittests)
Your own site
<a href="https://agentmods.dev/instructions/dotnet/maui/xaml-unittests"><img src="https://agentmods.dev/badge/instructions/dotnet/maui/xaml-unittests.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,149 This file is loaded in full into every session.
When invoked 1,149 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01149 $0.01149
Opus 5 $0.00575 $0.00575
Sonnet 5 $0.00230 $0.00230
Haiku 4.5 $0.00115 $0.00115

Measured 6d ago against content hash f2d2b67fb201, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

maui xaml-unittests.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 6d 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.

.github/instructions/xaml-unittests.instructions.md · 151 lines

How it starts

The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.

XAML Unit Testing Guidelines

This guide provides conventions for writing XAML unit tests in src/Controls/tests/Xaml.UnitTests/.

1. File Naming and Location for Issue Tests

When writing a test for a GitHub issue:

  • Location: Place the test file in the Issues/ folder
  • Naming convention: MauiXXXXX.xaml and MauiXXXXX.xaml.cs (where XXXXX is the GitHub issue number)

Example:

src/Controls/tests/Xaml.UnitTests/Issues/
├── Maui12345.xaml
└── Maui12345.xaml.cs

2. Basic Test Pattern

Most unit tests will:

  1. Check that the XAML page can be created/inflated
  2. Perform some assertions on the created page
  3. Apply to all [XamlInflator] test variations (runtime, XamlC, SourceGen)

XAML file (Maui12345.xaml):

<?xml version="1.0" encoding="utf-8" ?>
<ContentPage xmlns="http://schemas.microsoft.com/dotnet/2021/maui"
             xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
             x:Class="Microsoft.Maui.Controls.Xaml.UnitTests.Maui12345">
    <!-- Your test content -->
</ContentPage>

Code-behind (Maui12345.xaml.cs):

namespace Microsoft.Maui.Controls.Xaml.UnitTests;

public partial class Maui12345 : ContentPage
{
    public Maui12345()
    {
        InitializeComponent();
    }

    [TestFixture]
    class Tests
    {
        [Test]
        public void MyTest([Values] XamlInflator inflator)
        {
            var page = new Maui12345(inflator);
            Assert.That(page, Is.Not.Null);
            // Additional assertions
        }
    }
}

Note: Only add [SetUp] and [TearDown] methods if your test requires special initialization (e.g., setting up DispatcherProvider or Application.Current). Most tests don't need them.

3. Testing IL Correctness (XamlC) or Source Generation

When the test specifically validates compile-time behavior for a specific inflator:

XamlC (IL generation):

[Test]
public void MyTest([Values] XamlInflator inflator)
{
    if (inflator == XamlInflator.XamlC)
        Assert.Throws<BuildException>(() => MockCompiler.Compile(typeof(Maui12345)));
    else
    {
        var page = new Maui12345(inflator);
        Assert.That(page, Is.Not.Null);
    }
}

Read the full file on GitHub · 151 lines

Changes

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.

  1. 6d ago First seen · 151 lines · 1,149 tokens per session scan A f2d2b67fb201

Subscribe to this mod's changes

maui xaml-unittests.instructions.md is an instructions file published in the GitHub repository dotnet/maui (23,319 stars, last pushed today), licensed MIT. It adds 1,149 tokens to every session, about $0.0057 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.

Related

Other instructions, from other repositories

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.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens