.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.
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 skills/dotnet/maui/analyze-sessionsnpx skills add dotnet/maui --skill analyze-sessionsgit 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/skills/dotnet/maui/analyze-sessions)<a href="https://agentmods.dev/skills/dotnet/maui/analyze-sessions"><img src="https://agentmods.dev/badge/skills/dotnet/maui/analyze-sessions.svg" alt="Measured on agentmods" 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 | $0.00181 | $0.03435 |
| Opus 5 | $0.00090 | $0.01717 |
| Sonnet 5 | $0.00036 | $0.00687 |
| Haiku 4.5 | $0.00018 | $0.00344 |
Grade A, and why
analyze-sessions 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 5d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Sessions
Mines your local Copilot CLI session logs to find where agents waste effort or fail, then turns those findings into concrete repo edits + regression evals. It automates — for the whole fleet of your local sessions — a manual select → extract → judge → improve loop and the guard-eval mechanism shipped in PR #36002.
Trigger phrases: "analyze my recent maui sessions for agent improvements", "what's making my Copilot runs expensive / fail", "find recurring failure modes in my sessions", "turn my session failures into guard evals".
Do NOT use for: reviewing a single PR (use pr-review), running tests,
investigating CI failures (use azdo-build-investigator), or any informational
question — answer those directly.
Privacy contract (non-negotiable): This skill is local-only. It reads
~/.copilot/...and writes a redacted report into your session workspace. It NEVER opens a gist, NEVER POSTs a transcript, and NEVER ships session data to a third-party endpoint. The LLM-judge step runs inside your own Copilot session (your auth, your quota). Any cross-machine sharing is explicit, manual, opt-in — see Privacy & safety.
Architecture — one engine, two front doors
A deterministic PowerShell shared core does the heavy, reproducible work (select → extract → score → digest + redact). The judgment work (tag → cluster → propose → emit-eval) is done by you, the agent, reading the core's redacted output — no third-party endpoint is involved.
┌──────────────────────────────────────────────┐
local front door │ scripts/Get-SessionAnalysis.ps1 (NO LLM) │
-Repository/-Last│ select → extract → score → digest → redact │
-SessionId ─────►│ • dotnet-replay --summary --json (primary)│
│ • thin raw events.jsonl scan (supplemental)│
CI front door │ emits: session-analysis.md + .json contract│
-EventsDir ────►│ │
-EventsPath └───────────────────┬──────────────────────────┘
│ redacted digests + ranking
▼
┌──────────────────────────────────────────────┐
agent, in your │ judge → cluster → propose → emit-eval │
own session ─────►│ (rubric tagging, learn-from-pr taxonomy, │
│ vally guard-eval per recurring mode) │
└──────────────────────────────────────────────┘
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 285 lines · 181 tokens per session scan A c7b1bbd7e78f
analyze-sessions is a skill published in the GitHub repository dotnet/maui (23,319 stars, last pushed today), licensed MIT. It adds 181 tokens to every session and 3,435 once invoked, about $0.0009 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 skills, from other repositories
dpg-migration
Migration logic for Azure SDK for .NET data-plane libraries migrating from AutoRest/Swagger to TypeSpec-based generation. Uses MCP tools from the generator-agent server for automated deterministic fixes.
csharp-azure-spector-coverage-gaps
Discovers and implements gaps in Spector test coverage for the Azure C# HTTP client emitter. Use when asked to find missing Spector scenarios, add Spector test coverage, or implement a specific Spector spec for the Azure C# emitter. Can also compare coverage between the Azure dashboard and the Standard (TypeSpec core)…
auto-build-repair
Headless, bounded repair of custom-code build failures in an already-generated Azure SDK PR. Thin wrapper over the shared azure-sdk-mcp:azsdkcustomizedcodeupdate engine in custom-code-only scope (editScope: CustomCode); the skill owns the iterate-until-green loop, capped by a per-language maxIterations read from…
azure-sdk-mgmt-pr-review
Review Azure SDK management-plane pull requests, check naming conventions, API compatibility, and code quality.
mgmt-review-comment-resolution
Resolve review comments on Azure management-plane .NET SDK PRs. Handles renaming types/properties, changing property types, and other API surface adjustments by updating TypeSpec client.tsp and regenerating.
mitigate-breaking-changes
Patterns and techniques for mitigating breaking changes in Azure management-plane SDKs. Covers SDK-side customizations (partial classes, CodeGenType, CodeGenSuppress) and TypeSpec decorator customizations (clientName, access, markAsPageable, alternateType, hierarchyBuilding).