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-feedbackgit 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-feedback)<a href="https://agentmods.dev/skills/azure/azure-functions-skills/azure-functions-feedback"><img src="https://agentmods.dev/badge/skills/azure/azure-functions-skills/azure-functions-feedback/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-feedback"><img src="https://agentmods.dev/badge/skills/azure/azure-functions-skills/azure-functions-feedback.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 7 Skill instructs the agent to never refuse or to always comply. Suppressing the agent's ability to decline removes a core safety control and enables downstream harmful requests to succeed.Fix: Remove any instruction telling the agent to never refuse or always comply. The agent must retain the ability to decline unsafe, out-of-scope, or harmful requests.
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.00020 | $0.00893 |
| Opus 5 | $0.00010 | $0.00447 |
| Sonnet 5 | $0.00004 | $0.00179 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
azure-functions-feedback 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Language: Always respond in the same language the user is using.
azure-functions-feedback — Azure Functions Skills Feedback
Use this skill after an Azure Functions skill workflow when the session reveals an improvement opportunity for the azure-functions-* skills, their references, tests, README, or generated plugin payload.
When to use
Use this skill when:
- The user asks to send feedback, create an issue, or create a pull request for Azure Functions Skills.
- A workflow uncovered confusing guidance, missing verification, outdated commands, wrong MCP tool usage, repeated recovery steps, or missing diagnostics evidence.
- The agent needed user correction about an
azure-functions-*skill. - A manual or E2E test produced reusable findings.
Do not use it for ordinary app bugs unless the finding is about the skill suite itself.
Workflow
1. Review the session
Review the available conversation/session history, files changed, test output, and command results. Identify only actionable feedback related to this repository:
- affected skill or file (
azure-functions-create,azure-functions-deploy, README, routing, references, tests, etc.) - observed behavior
- expected behavior
- evidence from the session
- repro steps or scenario
- proposed fix or documentation change
- risk / impact
Redact secrets, tenant-specific sensitive data, function keys, publish profiles, tokens, connection strings, and customer data. Keep only resource names or URLs that the user explicitly allows to share.
2. Ask whether to proceed
If feedback is likely useful, ask the user whether they want to provide it. Keep the prompt concise:
I found feedback that could improve Azure Functions Skills. Would you like to preview it as an Issue or a Pull Request?
Options:
- Issue
- Pull Request
- Not now
Do not create external GitHub artifacts without explicit user confirmation.
3. Prepare a preview
Before creating anything, show a preview with this structure:
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 · 111 lines · 20 tokens per session scan A aeb080f524af
azure-functions-feedback is a skill published in the GitHub repository Azure/azure-functions-skills (17 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 893 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…