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-devflow-session-reviewgit 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-devflow-session-review)<a href="https://agentmods.dev/skills/dotnet/maui-labs/maui-devflow-session-review"><img src="https://agentmods.dev/badge/skills/dotnet/maui-labs/maui-devflow-session-review/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-labs/maui-devflow-session-review"><img src="https://agentmods.dev/badge/skills/dotnet/maui-labs/maui-devflow-session-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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 Excessive Agency · line 55 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00107 | $0.01978 |
| Opus 5 | $0.00053 | $0.00989 |
| Sonnet 5 | $0.00021 | $0.00396 |
| Haiku 4.5 | $0.00011 | $0.00198 |
Grade A, and why
maui-devflow-session-review 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 10d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MAUI DevFlow Session Review
Use this skill to turn prior MAUI DevFlow-assisted AI sessions into opt-in product feedback. The goal is not to fix bugs during the review; the goal is to identify where DevFlow caused friction, what workarounds were tried, and what outcome the agent eventually reached.
When to Use
Use this skill when:
- reviewing previous AI sessions that used
maui devflow - summarizing a long or stuck MAUI DevFlow debugging session
- finding repeated failed attempts, retries, or workarounds around DevFlow tools
- checking whether an advertised DevFlow feature did not work in practice
- preparing a markdown feedback report for MAUI DevFlow maintainers
- filing GitHub issues in
dotnet/maui-labsfrom session evidence - another DevFlow skill suggested an optional post-session feedback review
When to Stop
- The top actionable friction points are summarized with evidence, environment metadata, attempts, workaround, and final outcome.
- The markdown report is written or the requested GitHub issues are filed after a PII scrub.
- Remaining evidence would require scanning outside the user-approved scope.
- The finding is too ambiguous to classify without more context; label it unknown instead of continuing to mine private history.
Workflow
1. Confirm opt-in scope
If the user has provided session content directly in the message, start from step 4 (Classify friction) immediately — do not invoke live DevFlow CLI commands, search tools, or session history tools. The user has already supplied the evidence.
If no session content is provided, identify what the user wants reviewed:
- current session
- recent sessions matching MAUI DevFlow keywords
- a date range, target platform, feature, command family, or app framework
- sessions related to setup, connectivity, UI inspection, CDP, recording, logs, network, storage, profiler, or DevFlow Actions
Do not scan unrelated session history. This skill is opt-in telemetry: the user controls the scope and the output destination.
What ships with it
4 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.
- 10d ago First seen · 183 lines · 107 tokens per session scan A 6d6217c98c4e
maui-devflow-session-review is a skill published in the GitHub repository dotnet/maui-labs (213 stars, last pushed yesterday), licensed MIT. It adds 107 tokens to every session and 1,978 once invoked, about $0.0005 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-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-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.
argent-native-profiler
Native profiling for CPU hotspots, UI hangs, memory issues. iOS via xctrace; Android via Perfetto. Use when diagnosing native-level performance issues.
argent-react-native-app-workflow
Step-by-step workflows for developing or debugging React Native apps on iOS simulator or Android emulator. Use when starting the app, debugging Metro, fixing builds, diagnosing runtime errors, or running tests.
symbolication-setup
Configure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or source maps (React Native).
network-tracing
Instrument API requests with spans and distributed tracing. Use when tracking request latency, correlating client-backend traces, or debugging API issues.