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.
Borrowing it
Nothing to install: this file belongs to Azure/azure-functions-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Azure/azure-functions-skills/main/.github/skills/frd/SKILL.mdgit 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/frd)<a href="https://agentmods.dev/skills/azure/azure-functions-skills/frd"><img src="https://agentmods.dev/badge/skills/azure/azure-functions-skills/frd/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/frd"><img src="https://agentmods.dev/badge/skills/azure/azure-functions-skills/frd.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.00840 |
| Opus 5.5 | $0.00035 | $0.00336 |
| Sonnet 5.5 | $0.00017 | $0.00168 |
| Haiku 4.5 | $0.00009 | $0.00084 |
Grade A, and why
frd 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 1mo 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Requirement Documents
This is a repository development skill, not a distributed Azure Functions skill. Keep its workflow opt-in so ordinary development does not acquire an unsolicited documentation or approval gate.
Scope
Confirm that the user's request explicitly opts into FRD work. If it does not, continue the original task without creating an FRD or imposing FRD approval gates. Apply this process only to the feature or document the user selected, not to all work in the repository. A request to draft a document does not authorize feature implementation.
Authoring workflow
- Read the FRD process and index, the template, and any related FRD and its status. Inspect the relevant code and documentation before proposing a design.
- Update a related FRD where possible. Otherwise, use the next available
docs/frds/NNNN-kebab-case-title.mdand add it to the index. - Maintain one lifecycle FRD per canonical skill rather than one per enhancement, generated payload copy, or alias. Give cross-skill mechanisms a separate shared-infrastructure FRD when included in the user's selected scope. Do not create placeholder FRDs for unrelated skills.
- Complete all eight template sections, including stable requirement IDs, observable acceptance criteria, non-goals, design, decisions, tests, documentation impact, and status/sign-off. For skill designs, cover purpose, triggers, inputs/outputs, tools, transitions, safety boundaries, and evaluations.
- Record non-trivial decisions with alternatives, rationale, decision-maker, and date. Preserve earlier decisions and identify agent suggestions as proposals, not human approval. Make unresolved questions explicit.
- Keep committed documents in English and explanations in the user's language. Present the draft, open decisions, and review status; stop at the requested authoring scope.
Review and delivery for the opted-in scope
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.
- 1mo ago Changed · -3 lines 00ea023c8466
- 1mo ago First seen · 71 lines · 87 tokens per session scan A 8aeb2e203eb0
frd is a skill published in the GitHub repository Azure/azure-functions-skills (20 stars, last pushed yesterday), licensed MIT. It adds 87 tokens to every session and 840 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-09-12.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…