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/azure-functions-e2e-tests/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/azure-functions-e2e-tests)<a href="https://agentmods.dev/skills/azure/azure-functions-skills/azure-functions-e2e-tests"><img src="https://agentmods.dev/badge/skills/azure/azure-functions-skills/azure-functions-e2e-tests/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-e2e-tests"><img src="https://agentmods.dev/badge/skills/azure/azure-functions-skills/azure-functions-e2e-tests.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.00046 | $0.00855 |
| Opus 5 | $0.00023 | $0.00428 |
| Sonnet 5 | $0.00009 | $0.00171 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
azure-functions-e2e-tests 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 10d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Language: Reply in the user's language. Default generated reports to English unless the user asks for another language.
Azure Functions Skills E2E Tests
Prescriptive E2E runner for the package CLI's supported workspace-local distribution surface.
Execution protocol
- Read commands.md first.
- Create
reports/e2e/<run-id>/checklist.mdcontaining every command ID before execution. - Execute every numbered command individually and in order. Substitute only
$REPO,$CLI,$RUN, and$WS; translate shell syntax only when required by the operating system. - After each command, record the exact command, cwd, exit code, the first 200 lines of stdout, and stderr.
- Update the checklist after each command.
- Never mark a case as passing without evidence for all of its commands and criteria.
- Continue after failures, using a fresh workspace for each case.
- Do not add workaround commands. Record failures as failures.
Scope
The full matrix contains six local-mode cases:
| Scenario | GHCP | Claude | Codex |
|---|---|---|---|
Fresh install --local |
TC-S1-GHCP-LOCAL | TC-S1-CLAUDE-LOCAL | TC-S1-CODEX-LOCAL |
Replacement update --local |
TC-S2-GHCP-LOCAL | TC-S2-CLAUDE-LOCAL | TC-S2-CODEX-LOCAL |
The user may narrow by agent, scenario, or test-case ID. Otherwise run all six.
Plugin installation and coding-agent chat are intentionally out of scope: host tools install plugins, and this package no longer exposes chat.
Prerequisite gate
Only Node.js is required. Run node --version and stop if it fails. Coding-agent CLIs and credentials are not required because these tests validate generated workspace assets rather than host-managed plugin installation.
Preflight
Run and record the two PF commands from commands.md.
Report
Generate reports/e2e/<run-id>/report.html with:
- Summary cards and timestamps.
- A six-case matrix.
- Per-case collapsible evidence for every command.
- File verification and pass/fail analysis.
- Actionable issues.
expectedCommandCount,actualCommandCount, andmissingCommandIds.
What ships with it
3 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.
- 10d ago First seen · 95 lines · 46 tokens per session scan A 6fff87be0943
azure-functions-e2e-tests is a skill published in the GitHub repository Azure/azure-functions-skills (17 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 855 once invoked, about $0.0002 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
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…