Azure Functions Skills is a repository of agent skills, prompts, reusable definitions, MCP configuration, and telemetry hooks that give coding agents context about Azure Functions development and operations. Developers use it for guidance on triggers, bindings, runtimes, deployment, and code checks, while the catalogue contains its agent-facing add-ons.
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 Azure/azure-functions-skills --skill azure-functions-health-statusgit clone --depth 1 https://github.com/Azure/azure-functions-skillsWrote 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/azure/azure-functions-skills/azure-functions-health-status)<a href="https://agentmods.dev/skills/azure/azure-functions-skills/azure-functions-health-status"><img src="https://agentmods.dev/badge/skills/azure/azure-functions-skills/azure-functions-health-status/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/azure/azure-functions-skills/azure-functions-health-status"><img src="https://agentmods.dev/badge/skills/azure/azure-functions-skills/azure-functions-health-status.svg" alt="Reviewed on agentmods" width="80" 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.00060 | $0.00867 |
| Opus 5 | $0.00030 | $0.00434 |
| Sonnet 5 | $0.00012 | $0.00173 |
| Haiku 4.5 | $0.00006 | $0.00087 |
Grade A, and why
azure-functions-health-status 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 12d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Functions Health Status
Use this skill to investigate the current status and health of an existing Azure Function App.
Write final answers in the user's language.
Required interaction
Ask only for missing inputs that are needed to identify the app and time window:
- Function App name (required unless already provided)
- Subscription ID or name (optional)
- Resource group (optional)
- Investigation time window, default
24h(optional)
If subscription or resource group is unknown, discover them with Resource Graph. If multiple matching apps are found, ask the user to choose one.
Fast path
- Call Azure best practices for
azurefunctionsfirst when available. - Run the bundled health script for the current shell/OS:
scripts/get-functionapp-health-status.ps1 -AppName <app-name>scripts/get-functionapp-health-status.sh -a <app-name>on macOS/Linux or Bash- Add
-SubscriptionId <sub>and/or-ResourceGroup <rg>when known. - Add
-Hours <n>when the user requests a specific time window. - For Bash, use
-s <sub>,-g <resource-group>, and/or-H <hours>when known. - Bash script requires Azure CLI plus a working
python3orpythonexecutable for JSON shaping.
- If bundled script execution is unavailable, use
references/health-status-commands-and-kql.md. - Report health findings and action items; avoid dumping raw logs unless requested.
If health findings require runtime or trigger-specific interpretation, use ../azure-functions-common/references/routing.md on demand. Do not load shared language/extension references for plain status output.
Scope boundary
This skill should collect:
- Current app state: enabled/running/stopped, metadata availability, runtime availability
- Plan status and Resource Health result
- Azure Monitor metrics: instance count, CPU, memory, execution counts/units, always-ready units
- Trigger status summary and notable disabled or indexing-failed functions
- Application Insights/Log Analytics: request counts/failures/p95, dependency failures, exceptions, warning/error traces
- Recent Activity Log events
- Gaps: missing telemetry, unsupported Resource Health, unavailable diagnostic data
What ships with it
3 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.
- 12d ago First seen · 77 lines · 60 tokens per session scan A d0815bd5f58b
azure-functions-health-status is a skill published in the GitHub repository Azure/azure-functions-skills (17 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 867 once invoked, about $0.0003 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
gke-ai-troubleshooting-jobset-interruption
Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or…
gke-workload-troubleshooting
Diagnoses GKE workload failures (CrashLoopBackOff, OOMKilled, ImagePullBackOff, Pending, etc.) via logs and events. Use when pods fail to start or crash repeatedly. Don't use for GKE cluster infrastructure provisioning, node pool creation, or non-Kubernetes Google Cloud services.
gke-node-notready
Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't…
gke-ai-troubleshooting-handle-disruption-gpu-tpu
Diagnoses, predicts, and mitigates node disruptions during Compute Engine host maintenance and hardware or software maintenance events for GPU and TPU workloads on GKE. Use when diagnosing node disruptions, predicting host maintenance events on GPU/TPU nodepools, inspecting node interruption PromQL metrics, auditing…
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
troubleshoot-sandbox
Troubleshoot OpenSandbox issues by running diagnostics (logs, inspect, events, summary) via CLI or HTTP API to diagnose sandbox failures like OOM, crash, image pull errors, network problems, etc.