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 zmustafa/AzureSupportAgent --skill network-diagnosticsgit clone --depth 1 https://github.com/zmustafa/AzureSupportAgentWrote 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/zmustafa/azuresupportagent/network-diagnostics)<a href="https://agentmods.dev/skills/zmustafa/azuresupportagent/network-diagnostics"><img src="https://agentmods.dev/badge/skills/zmustafa/azuresupportagent/network-diagnostics.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.00029 | $0.00226 |
| Opus 5 | $0.00015 | $0.00113 |
| Sonnet 5 | $0.00006 | $0.00045 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
Network 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 8d 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.
What it actually says
Network diagnostics
- Define source, destination, protocol, port, SNI/host header, path, expected resolution, and failure time.
- Test in layers: DNS, route, ICMP when meaningful, TCP, TLS, then HTTP/application behavior.
- Correlate effective routes, NSGs, Azure Firewall, peering, private DNS links, private endpoints, load balancers, and application gateways.
- Prefer a sandbox inside the workload VNet for private-path evidence; public platform probes cannot prove private reachability.
- Treat ping loss as inconclusive where ICMP is blocked; a successful TCP/TLS probe is stronger evidence.
- Record exact observed status, address, certificate/SNI result, and failing hop/control.
- Recommend the smallest reversible correction and keep network mutations behind approval.
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.
- 8d ago First seen · 16 lines · 29 tokens per session scan A 234b1be9ec5d
Network diagnostics is a skill published in the GitHub repository zmustafa/AzureSupportAgent (45 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 226 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-08-30.
Other skills, from other repositories
azure-messaging
Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue…
azure-messaging
Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue…
adding-azure-communication-services-email
Adds transactional email to an Azure web app via Azure Communication Services (ACS) Email — verification emails, password resets, notifications. Encodes the three ACS quirks that consistently break Bicep deploys (location:'global' literal, dataLocation in plain English not Azure region IDs, declare-order to avoid…
deploying-fc1-flex-consumption-functions
Deploys standalone Azure Function Apps on Flex Consumption (FC1) for workloads SWA managed functions can't handle — timer triggers, queue triggers, AI workloads, long-running operations. Provisions via ARM REST API or Bicep because az CLI flags silently fall back to deprecated Y1/Dynamic. Includes the…
curating-azure-deployment-learnings
Captures Azure deployment learnings from real projects in a structured format and promotes recurring ones into the diagnosing-azure-deployment-failures gotcha catalogue. Provides scripts to capture a new learning (with project, severity, frontmatter), diff against existing gotchas, and propose promotions with…
diagnosing-azure-deployment-failures
Matches Azure deploy / CI / runtime failures against 37+ documented gotchas with verified fixes (BCP258, AADSTS70021, sqlcmd-not-found, FC1-CLI-silent-fallback, ACS dataLocation quirks, SSE timeouts, and more). Delegates to Microsoft's azure-diagnostics for live log/metric queries. Use when a deploy fails, a deployed…