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.
git clone --depth 1 https://github.com/WYRE-AI/msp-claude-pluginsWrote 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/commands/wyre-ai/msp-claude-plugins/azure-diagnostics)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/azure-diagnostics"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/azure-diagnostics.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.1 | $0.00027 | $0.00592 |
| Opus 5 | $0.00014 | $0.00296 |
| Sonnet 5 | $0.00005 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
azure-diagnostics 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 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.
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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Diagnostics Triage
Runs a focused, read-only diagnostics pass over an Azure resource, resource group, or subscription. Use it for "is something wrong with [resource]?" investigations, incident triage, and post-incident review.
This command is read-only — it diagnoses and reports; it never restarts, reconfigures, or remediates a resource.
Arguments
target(required) — Azure resource ID, resource group, or subscription ID to triagewindow(optional) — Lookback window for alerts and metrics (e.g. 1h, 24h, 7d) — defaults to 24h
What it checks
- Resource Health —
resourcehealthfor the current availability state (Available/Degraded/Unavailable/Unknown) and the reason classification (platform-initiated, customer-initiated, unplanned). Surfaces any active subscription-level health events. - AppLens diagnostics — when Resource Health is degraded or the picture is unclear, run
applensdetectors against the resource to identify the tripped detector, the failing dependency, and Microsoft's recommended mitigation. - Monitor alerts —
monitorto list alert rules covering the target and their fired/resolved state within the lookback window. - Supporting metrics — pull relevant
monitormetric series (and, where useful, a bounded Log Analytics KQL query) around the incident window to confirm and quantify impact.
Output
A triage report covering:
- Verdict — healthy, degraded, or unavailable, with the most likely cause
- Azure-side vs. customer-side — whether a platform-initiated event explains the symptom (nothing to fix customer-side) or a customer-side cause needs action
- Evidence — the AppLens detector results, fired alerts, and metric/log excerpts that support the verdict
- Recommended next steps — what to do, explicitly noting that any fix happens through a separate write-capable path, not this connector
Caveats
- Read-only. This command cannot acknowledge alerts, restart resources, or apply fixes. It identifies the problem and the recommended action; execution is out of scope for the
azure-mcpconnector. - Scope the
windowto the incident — a wide window dilutes the signal and slows queries.
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 · 42 lines · 27 tokens per session scan A 69d2cfd0b46e
azure-diagnostics is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 5d ago), licensed Apache-2.0. It adds 27 tokens to every session and 592 once invoked, about $0.0001 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-09-04.
Other commands, from other repositories
System Status
Check overall system health and status.
investigate
Start a deep root-cause investigation on the AWS DevOps Agent and stream progress.
cloudflare-queues:troubleshoot
Quick troubleshooting for common Cloudflare Queues issues.
cloudflare-workers:debug
Interactive debugging workflow for Cloudflare Workers. Diagnoses deployment errors, runtime issues, and performance problems with step-by-step fixes.
cloudflare-workflows:debug
Interactive debugging for failing workflow instances. Use when user reports workflow errors, instances stuck, or deployment failures.
coolify-debug
Diagnose Coolify deployment issues.