.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/skills/analyze-sessions/SKILL.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/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/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/skills/dotnet/maui/analyze-sessions"><img src="https://agentmods.dev/badge/skills/dotnet/maui/analyze-sessions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 185 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00181 | $0.03438 |
| Opus 5.5 | $0.00072 | $0.01375 |
| Sonnet 5.5 | $0.00036 | $0.00688 |
| 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 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 — 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.
- 1mo ago Changed fb650a13b1d8
- 1mo 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,322 stars, last pushed today), licensed MIT. It adds 181 tokens to every session and 3,438 once invoked, about $0.0007 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 skills, from other repositories
generate-code-cs
Generate the code from typespec for C#. Parameter: C# SDK repository root location .
build-sample-matrix
Build the matrix of all the samples throughout different frameworks.
translate-a-sample
Translate the Azure SDK sample from python to C# and generate markdownn file for the sample. Parameters: C# SDK repository root; python SDK repository root; Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; The name of sample file in Python SDK repository.
author-test
Generate a test given sample. Parameters: C# SDK repository root; Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; the sample to use as a starting point for the test.
update-changelog
Update the CHANGELOG.md files of C# projects. Parameters: csroot C# SDK repository root.
budget-checker
Validates that a proposed trip fits within the user's stated budget.