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/prompts/checklist-plan.prompt.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/commands/azure/azure-functions-skills/checklist-plan)<a href="https://agentmods.dev/commands/azure/azure-functions-skills/checklist-plan"><img src="https://agentmods.dev/badge/commands/azure/azure-functions-skills/checklist-plan/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/commands/azure/azure-functions-skills/checklist-plan"><img src="https://agentmods.dev/badge/commands/azure/azure-functions-skills/checklist-plan.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.00015 | $0.00169 |
| Opus 5.5 | $0.00006 | $0.00068 |
| Sonnet 5.5 | $0.00003 | $0.00034 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
checklist-plan 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.
What it actually says
Analyze the task and create an implementation plan following this structure:
- Investigate — survey the affected files and understand the current behavior.
- Plan — produce a numbered checklist in
plan.mdwith clear, actionable steps. - Execute — work through each step one at a time; mark each item done as you go.
- Verify — after all steps, run
npm run checkand confirm everything passes.
For code changes, follow TDD: write a failing test before implementing each step. For non-code tasks (skills, CI, docs), skip TDD but still verify at the end.
Update the checklist after completing each step so progress is always visible.
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 First seen · 17 lines · 15 tokens per session scan A 45d1df53df47
checklist-plan is a command published in the GitHub repository Azure/azure-functions-skills (20 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 169 once invoked, about $0.0001 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-09.
Other commands, from other repositories
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.
tdd
Canon TDD (specify, encode, fulfill) with one test at a time, approval gates, and kitchen-cleaning refactor when needed.