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 agentmods add instructions/dotnet/maui/uitestsgit clone --depth 1 https://github.com/dotnet/mauiWhat 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 | $0.07172 | $0.07172 |
| Opus 5 | $0.03586 | $0.03586 |
| Sonnet 5 | $0.01434 | $0.01434 |
| Haiku 4.5 | $0.00717 | $0.00717 |
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 yesterday.
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 — 776 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 appropriate
[Category(UITestCategories.XYZ)]attributes (only ONE per test) - Test should validate expected behavior through UI interactions and assertions
- Create corresponding Appium-based NUnit tests that inherit from
Base Class and Infrastructure
- Each test class must inherit from
_IssuesUITest - The
_IssuesUITestbase class provides:- The
Appproperty for interacting with UI elements - Test initialization and setup
- Helper methods for common UI test operations
- The
- The test infrastructure automatically handles platform detection and page navigation
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.
- yesterday 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,317 stars, last pushed yesterday), licensed MIT. It adds 7,172 tokens to every session, about $0.0359 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 instructions, from other repositories
azure-sdk-for-net AGENTS.md
Instructions for Azure/azure-sdk-for-net, covering azure sdk for .net - ai agent guidelines, repository overview, purpose and scope, repository structure and agent interaction guidelines.
azure-sdk-for-net copilot-instructions.md
Instructions for Azure/azure-sdk-for-net, covering project overview, prerequisites, folder structure, azure generator and azure management generator.
BlazorBindings.Maui AGENTS.md
Instructions for Dreamescaper/BlazorBindings.Maui, covering mobile guidelines, platform, razor and component conventions and blazor bindings generation.
Enclave-Terminal-Breach CLAUDE.md
Instructions for Gwergilius/Enclave-Terminal-Breach, covering enclave terminal breach – claude code configuration, rules and quick reference.
vscode tree-widgets.instructions.md
Use when asked to consume workbench tree widgets in VS Code.
vscode accessibility.instructions.md
Use when implementing accessibility features, ARIA labels, screen reader support, accessible help dialogs, or keybinding scoping for accessibility. Covers AccessibleContentProvider, CONTEXTACCESSIBILITYMODEENABLED, verbosity settings, and announcement patterns.