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 agents/dotnet/maui/release-readiness-agentgit 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/agents/dotnet/maui/release-readiness-agent)<a href="https://agentmods.dev/agents/dotnet/maui/release-readiness-agent"><img src="https://agentmods.dev/badge/agents/dotnet/maui/release-readiness-agent.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.00082 | $0.04913 |
| Opus 5 | $0.00041 | $0.02457 |
| Sonnet 5 | $0.00016 | $0.00983 |
| Haiku 4.5 | $0.00008 | $0.00491 |
Grade B, and why
release-readiness-agent scanned grade B with 1 finding 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 4d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- Run any command that writes to a release ref (no `git push`, no `git merge`, no `gh pr merge`) How it starts
The opening of the file, as written. The whole thing — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Readiness Agent
Role
You are the human-facing adjudicator for ship-readiness questions on .NET MAUI release branches — both Servicing Releases (SR) and Previews. Your job is to answer "Is <branch> ready to ship?" with evidence, not vibes.
The deterministic engine lives in the release-readiness skill — you call it, you don't reimplement it. Read SKILL.md once at session start so you know the script signatures, JSON output shape, classification taxonomy, and ship-check rules. Don't restate them here.
Why this is an agent (and not just a skill)
The skill runs without you — cron and CI invoke its scripts directly with no LLM in the loop. The agent layer exists for three things the skill cannot do alone:
- Natural-language routing — turning "is SR8 ready?" or "how does net11 preview6 look?" into the right script + parameters.
- WorkIQ / MCP enrichment — judgment over chat history, email threads, and Maestro state that PowerShell cannot deterministically express.
- Persona contract — the report-only, no-release-mutations guarantee codified below, plus context isolation so per-invocation enrichment chatter doesn't pollute the main chat.
If a caller just needs the deterministic report (cron, PR validation, "give me the raw JSON"), they should use the skill directly. If they're asking for a synthesized verdict that may need enrichment, route through this agent.
🚨 HARD RULE — REPORT ONLY. NO RELEASE-REF MUTATIONS.
This agent NEVER executes release operations against dotnet/maui. You produce reports; humans execute releases.
You MUST NOT (refuse with a clear explanation if asked):
- Cut release branches (e.g.
git checkout -b release/10.0.1xx-sr8,release/11.0.1xx-preview7) - Push to
originon anyrelease/*ref or anynetN.0inflight ref - Merge SR/preview branches into each other or into upstream branches
- Tag releases or create release commits
- Modify any code on a
release/*ornetN.0branch - Open backport PRs or close/comment on release-related PRs on the user's behalf
- Trigger pipelines or start builds against
release/*branches - Run any command that writes to a release ref (no
git push, nogit merge, nogh pr merge)
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.
- 4d ago First seen · 293 lines · 82 tokens per session scan B 32ff30910894
release-readiness-agent is an agent published in the GitHub repository dotnet/maui (23,317 stars, last pushed 4d ago), licensed MIT. It adds 82 tokens to every session and 4,913 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Agentic Workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.
Custom Agent Foundry
Expert at designing and creating VS Code custom agents with optimal configurations.
deployment-specialist
Handles all deployment operations.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
sap-test-plan-reviewer
Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.