AI Dev Gallery is an open-source Windows application that teaches developers how to add AI features using local models and APIs. Windows developers use its interactive samples to explore models and export C# Visual Studio projects.
Borrowing it
Nothing to install: this file belongs to microsoft/ai-dev-gallery. 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/microsoft/ai-dev-gallery/main/.github/instructions/adding-xaml.instructions.mdgit clone --depth 1 https://github.com/microsoft/ai-dev-galleryWrote 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/microsoft/ai-dev-gallery/adding-xaml)<a href="https://agentmods.dev/instructions/microsoft/ai-dev-gallery/adding-xaml"><img src="https://agentmods.dev/badge/instructions/microsoft/ai-dev-gallery/adding-xaml/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/microsoft/ai-dev-gallery/adding-xaml"><img src="https://agentmods.dev/badge/instructions/microsoft/ai-dev-gallery/adding-xaml.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.00200 | $0.00200 |
| Opus 5.5 | $0.00080 | $0.00080 |
| Sonnet 5.5 | $0.00040 | $0.00040 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
ai-dev-gallery adding-xaml.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 2mo 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.
What it actually says
XAML UI Instructions
When reviewing or modifying XAML files in AI Dev Gallery:
WinUI 3 Standards
This project uses WinUI 3 with Windows App SDK. Use WinUI controls, not UWP controls.
Accessibility Requirements
All Interactive Elements
- Must be keyboard navigable (
IsTabStop="True"where needed) - Must have accessible names (
AutomationProperties.Name) - Must support high contrast themes
Screen Reader Support
Use NarratorHelper in code-behind for dynamic announcements:
NarratorHelper.Announce(control, "Message", "UniqueAnnouncementId");
Code Review Checks
- All controls have appropriate
x:Nameif referenced in code - Interactive elements are keyboard accessible
AutomationProperties.Nameset for screen readers- Proper use of Grid/StackPanel for layout
- Responsive design considerations
- High contrast theme compatibility
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.
- 2mo ago First seen · 34 lines · 200 tokens per session scan A 59faba6addcb
ai-dev-gallery adding-xaml.instructions.md is an instructions file published in the GitHub repository microsoft/ai-dev-gallery (1,515 stars, last pushed 12d ago), licensed MIT. It adds 200 tokens to every session, about $0.0008 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
plan-forge dapr.instructions.md
Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core 10, parameterized queries, migration strategy.
plan-forge naming.instructions.md
Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.
plan-forge caching.instructions.md
Caching patterns for .NET — IDistributedCache, Redis, in-memory, cache-aside, TTL strategies.
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.