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-best-practicesgit 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-best-practices)<a href="https://agentmods.dev/skills/azure/azure-functions-skills/azure-functions-best-practices"><img src="https://agentmods.dev/badge/skills/azure/azure-functions-skills/azure-functions-best-practices/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-best-practices"><img src="https://agentmods.dev/badge/skills/azure/azure-functions-skills/azure-functions-best-practices.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.00053 | $0.01257 |
| Opus 5 | $0.00026 | $0.00629 |
| Sonnet 5 | $0.00011 | $0.00251 |
| Haiku 4.5 | $0.00005 | $0.00126 |
Grade A, and why
azure-functions-best-practices 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Functions Best Practices Review
Use this skill to review an existing Azure Function App, prioritize best-practice findings, and help apply approved remediations.
Write final answers in the user's language.
When to use
- Review my Function App for best practices
- Improve or harden an existing Azure Functions app
- Check whether a Function App follows recommended settings
- Suggest safe fixes for Function App configuration, runtime, scale, security, or observability
- Prepare a best-practices report before production readiness review
Do not use for
- Creating a new Function App: use
azure-functions-create - Static inventory only: use
azure-functions-inventory - Current health/status only: use
azure-functions-health-status - Active incident root-cause analysis: use
azure-functions-diagnostics - Deployment-only tasks: use
azure-functions-deploy - Generic Azure compliance scans: use Azure-wide compliance tooling when available
Core principles
- Evidence first — do not recommend changes until app inventory is collected.
- MCP guidance first — before scoring findings, call the Azure best-practices MCP guidance for Azure Functions (
get_azure_bestpractices/get_azure_bestpractices_getwithresource: azurefunctionsandaction: all) when the tool is available. - Report before remediation — present findings and ask which fixes to apply.
- Approval-gated changes — do not update app settings, restart apps, deploy code, change networking, change identity/RBAC, or modify source/IaC without explicit user approval.
- Load references on demand — use
azure-functions-commonrouting to load only relevant language and trigger/binding references. - Redact secrets — report setting names and presence only; never reveal values.
Required best-practices guidance
Treat Azure best-practices MCP output as the authoritative current guidance layer for this skill. Always attempt to retrieve it before producing the review report, unless the tool is unavailable. If it is unavailable, state that the MCP guidance could not be loaded and continue with the local checklist as a fallback.
What ships with it
2 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 · 108 lines · 53 tokens per session scan A 9ffe6cae1546
azure-functions-best-practices is a skill published in the GitHub repository Azure/azure-functions-skills (17 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 1,257 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-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…