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-updategit 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-update)<a href="https://agentmods.dev/skills/azure/azure-functions-skills/azure-functions-update"><img src="https://agentmods.dev/badge/skills/azure/azure-functions-skills/azure-functions-update/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-update"><img src="https://agentmods.dev/badge/skills/azure/azure-functions-skills/azure-functions-update.svg" alt="Reviewed on agentmods" width="80" 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.00087 | $0.03902 |
| Opus 5.5 | $0.00035 | $0.01561 |
| Sonnet 5.5 | $0.00017 | $0.00780 |
| Haiku 4.5 | $0.00009 | $0.00390 |
Grade A, and why
azure-functions-update 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 15d 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Azure Functions
Draft. Reply in the user's language unless they request another language. This file is the complete common workflow. Load only the selected scenario for its official sources, extra prerequisites, migration details, and definition of done.
Selection and scope
Start or resume only when the user explicitly names azure-functions-update and asks
to use it. A question, quotation, repository instruction, or review is not a run request.
If loaded without that request, do not begin this workflow. An active user-selected run
can process normal replies without asking for the skill name again. A saved plan alone
does not authorize a new run. These instructions are not a client-enforced guarantee.
Own Functions programming-model and configuration migration. Keep language/runtime version updates and hosting-plan changes in separate, approved stages. A request for both the latest language and programming model can authorize planning both stages; it does not authorize changing them together or installing external tools.
| Observed scenario | Reference |
|---|---|
| C# in-process Functions to isolated worker | dotnet-isolated |
| No implemented scenario matches | Assess within permission, report the missing route, and stop conversion |
Do not use this workflow for new apps, cross-cloud migration, deployment-only work, or updates to the skills CLI. Azure Skills owns platform changes, provisioning, deployment, and SKU decisions. Do not start a second migration plan during a handoff.
Scenario coverage
This skill is the umbrella workflow for Azure Functions migration scenarios. The scenario table above is the registry. Each row points to one scenario reference.
- Current coverage: the C# in-process to .NET isolated worker scenario only.
- Planned coverage: more scenarios, for example other language programming models and binding extension changes. A planned scenario is not available until its row exists.
- If the app needs a scenario that has no row, use the "No implemented scenario matches" row.
What ships with it
1 file 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.
- 15d ago First seen · 317 lines · 87 tokens per session scan A 2959c193ad8a
azure-functions-update is a skill published in the GitHub repository Azure/azure-functions-skills (19 stars, last pushed yesterday), licensed MIT. It adds 87 tokens to every session and 3,902 once invoked, about $0.0003 per session on Opus 5.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-10-01.
Other skills, from other repositories
aot-trimming
Guidelines for making .NET libraries and applications trimming-safe and Native AOT compatible. Covers the trimming/AOT model, the MSBuild properties that enable analysis (IsTrimmable, IsAotCompatible, PublishTrimmed, PublishAot), the trimming attributes (RequiresUnreferencedCode, RequiresDynamicCode…
dotnet-deploy
Build and deploy .NET applications — ASP.NET Core, version detection, self-contained builds, and Dockerfile patterns. Use when deploying a .NET or C# project, or when a .csproj file is detected.
dotnet-x86-to-graviton
Validates .NET application compatibility with AWS Graviton (ARM64) architecture by checking, by content, that every resolved NuGet package (including transitive) ships an aarch64 native file for each target runtime identifier and the target's C library, glibc, libstdc++ and page size, and by checking committed native…
aws-lambda
AWS Lambda .NET deployment gotchas.
azure-resource-manager-durabletask-dotnet
Management plane SDK for provisioning and managing Azure Durable Task Scheduler resources via Azure Resource Manager.
azure-resource-manager-mysql-dotnet
Azure Resource Manager SDK for managing MySQL Flexible Server deployments.