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 skills add dotnet/maui-labs --skill maui-release-notesgit clone --depth 1 https://github.com/dotnet/maui-labsWrote 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-labs/maui-release-notes)<a href="https://agentmods.dev/skills/dotnet/maui-labs/maui-release-notes"><img src="https://agentmods.dev/badge/skills/dotnet/maui-labs/maui-release-notes.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00073 | $0.00946 |
| Opus 5 | $0.00036 | $0.00473 |
| Sonnet 5 | $0.00015 | $0.00189 |
| Haiku 4.5 | $0.00007 | $0.00095 |
Grade A, and why
maui-release-notes 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MAUI Release Notes
Use this skill when an app team needs to answer: "What does this .NET or MAUI release mean for our app?" Focus on adoption guidance for app developers, QA, and CI owners rather than on shipping the MAUI SDK itself.
Response Checklist
- Keep the audience app-focused: repo owners, app developers, QA, and CI owners.
- Convert release notes into concrete app actions (SDK/workload/tooling updates, risks, and validation plan), not maintainer publishing tasks.
- Use
dotnet-workload-infowhen exact workload or environment dependency data is needed.
Typical Inputs
- The app's current .NET version, workload set, and MAUI package baseline.
- The target release the team is considering.
- Platforms in scope: Android, iOS, Mac Catalyst, macOS, Windows.
- Whether the output should be a short summary, an upgrade checklist, or rollout guidance.
If exact workload, package, Xcode, JDK, or Android SDK version data is missing,
use dotnet-workload-info to confirm it. Use live version discovery to support
app upgrade planning, not to dump maintainer-only manifest data unless the user
explicitly asks for it.
What to Extract from Release Notes
- Breaking changes or deprecations that affect app code, project files, or deployment.
- Required environment updates such as Xcode, JDK, Android SDK, Visual Studio, or workload-set changes that affect building or shipping the app.
- MAUI package, workload, or CI updates the app repo needs.
- Known issues, regressions, or unsupported combinations that could block the upgrade.
- Validation work the app team should plan after the upgrade.
- Rollback considerations if the new release introduces app-specific risk.
Recommended Workflow
- Establish the app's current baseline: target framework, workloads, packages, CI image/tooling, and supported platforms.
- Read the official .NET and MAUI release notes for the target release.
- Pull only the changes that are relevant to app builders: environment requirements, app-facing breaking changes, tooling shifts, and known issues.
- Use
dotnet-workload-infowhen the team needs exact upgrade commands or authoritative workload dependency requirements. - Translate the release into app-specific actions, risks, and tests instead of repeating framework internals.
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 Changed · -46 tokens per session 3ea1fda28752
- 9d ago First seen · 110 lines · 119 tokens per session scan A 8f00970000de
maui-release-notes is a skill published in the GitHub repository dotnet/maui-labs (213 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 946 once invoked, about $0.0004 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
argent-device-interact
Interact with an iOS simulator, Android emulator, or Chromium (CDP) app using argent MCP tools. Use when tapping UI elements, performing gestures, scrolling/swiping, typing text, pressing hardware buttons, launching apps, opening URLs, taking screenshots, waiting for an element to appear or disappear, or checking…
argent-metro-debugger
Debug a JS runtime via CDP using argent debugger tools. Primary path is React Native via Metro (iOS / Android / Vega); a subset of the tools (debugger-connect, debugger-status, debugger-evaluate, debugger-log-registry) also drive a Chromium (CDP) app's renderer (an Electron app, or any Chromium browser exposing CDP)…
argent-settings-permissions
Grant, deny, or reset an app's runtime permissions (camera, microphone, photos, contacts, notifications, calendar, location, location-always, media-library, motion, reminders) on an iOS simulator or Android device using the argent settings-permissions tool - without navigating the system Settings UI. Use when the…
argent-react-native-optimization
Optimizes a React Native app by profiling first to find real bottlenecks, then sweeping for mechanical issues. Entry-point for all performance work. Use when the app feels slow, user asks to optimize, fix re-renders, reduce jank, or improve startup. Delegates to argent-react-native-profiler for measurement.
mobile-automation
Control Android and iOS devices, emulators and simulators — launch apps, tap, swipe, type, take screenshots, read the accessibility tree. Use when a task involves a mobile device or app, mobile UI testing, or reproducing a bug on a phone.
argent-react-native-profiler
Profile a React Native Hermes app to measure re-render and CPU performance using argent profiler tools. Use when optimizing for performance, measuring before/after a fix, spotting slow components, diagnosing re-renders, checking CPU hotspots, or producing a ranked issue report.