.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/collectionview-handler-detection.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/collectionview-handler-detection)<a href="https://agentmods.dev/instructions/dotnet/maui/collectionview-handler-detection"><img src="https://agentmods.dev/badge/instructions/dotnet/maui/collectionview-handler-detection/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/collectionview-handler-detection"><img src="https://agentmods.dev/badge/instructions/dotnet/maui/collectionview-handler-detection.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.00890 | $0.00890 |
| Opus 5.5 | $0.00356 | $0.00356 |
| Sonnet 5.5 | $0.00178 | $0.00178 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
maui collectionview-handler-detection.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 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CollectionView Handler Detection
Handler Implementation Status
There are TWO separate handler implementations, but they apply to different platforms:
- Items/ (
Handlers/Items/) - Contains code for ALL platforms (Android, iOS, Windows, MacCatalyst, Tizen) - Items2/ (
Handlers/Items2/) - Contains code for iOS/MacCatalyst ONLY
Platform-Specific Deprecation
The deprecation of Items/ only applies to iOS/MacCatalyst:
| Platform | Active Handler | Notes |
|---|---|---|
| Android | Items/Android/ |
ONLY implementation - Items2/ has no Android code |
| Windows | Items/ |
ONLY implementation - Items2/ has no Windows code |
| iOS | Items2/iOS/ |
Items/ iOS code is deprecated |
| MacCatalyst | Items2/iOS/ |
Items/ MacCatalyst code is deprecated |
CRITICAL: Items2/ is iOS/MacCatalyst only. There is NO Items2/ code for Android or Windows.
Which Handler to Work On
Decision Tree by Platform
Is the issue/PR for Android or Windows?
YES → Work on Items/ (it's the ONLY implementation)
NO → Continue...
Is the issue/PR for iOS or MacCatalyst?
YES → Work on Items2/ (Items/ is deprecated for iOS)
NO → Check platform and find appropriate handler
Detection Algorithm
Check which handler directory the files are in:
# Check changed files in a PR
git diff <base-branch>..<pr-branch> --name-only | grep -i "handlers/items"
# Look for path pattern:
# - Contains "/Items/Android/" → Android (ONLY implementation, work here)
# - Contains "/Items/Windows/" or ".Windows.cs" → Windows (ONLY implementation, work here)
# - Contains "/Items2/iOS/" or "Items2/*.iOS.cs" → iOS/MacCatalyst (CURRENT)
# - Contains "/Items/*.iOS.cs" (not Items2) → iOS (DEPRECATED, prefer Items2/)
Default Behavior by Platform
| Platform | Default Action |
|---|---|
| Android | ✅ Work on Items/Android/ - it's the only option |
| Windows | ✅ Work on Items/ Windows files - it's the only option |
| iOS/MacCatalyst | ✅ Work on Items2/ - Items/ is deprecated for iOS |
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 First seen · 96 lines · 890 tokens per session scan A f791f09db370
maui collectionview-handler-detection.instructions.md is an instructions file published in the GitHub repository dotnet/maui (23,322 stars, last pushed today), licensed MIT. It adds 890 tokens to every session, about $0.0036 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 swiftui.instructions.md
SwiftUI patterns — state management, navigation, async data loading, previews.
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.
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).