Azure Developer CLI (azd) is a command-line tool for building, deploying, and operating applications on Azure. Developers use it to move through application workflows such as coding, building, deployment, and monitoring with Azure templates and resources. Its catalogue entries help AI agents work with azd and Azure application projects.
Borrowing it
Nothing to install: this file belongs to Azure/azure-dev. 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-dev/main/.github/skills/foundry-extension-scenario-pr-regression/SKILL.mdgit clone --depth 1 https://github.com/Azure/azure-devWrote 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-dev/foundry-extension-scenario-pr-regression)<a href="https://agentmods.dev/skills/azure/azure-dev/foundry-extension-scenario-pr-regression"><img src="https://agentmods.dev/badge/skills/azure/azure-dev/foundry-extension-scenario-pr-regression/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-dev/foundry-extension-scenario-pr-regression"><img src="https://agentmods.dev/badge/skills/azure/azure-dev/foundry-extension-scenario-pr-regression.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.00231 | $0.01402 |
| Opus 5.5 | $0.00092 | $0.00561 |
| Sonnet 5.5 | $0.00046 | $0.00280 |
| Haiku 4.5 | $0.00023 | $0.00140 |
Grade A, and why
foundry-extension-scenario-pr-regression 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
foundry-extension-scenario-pr-regression
Runs the azure.ai.agents extension's interactive CLI scenarios as a local
PR regression gate and reports the results back on the pull request.
Overview
The azure.ai.agents extension ships goal-based scenarios for the
cli-interactive-tester
MCP server under cli/azd/extensions/azure.ai.agents/tests/cli-interactive-tester-scenarios/.
These scenarios are never run in CI — they need the tester MCP server, a populated
profile.local.yaml, manual az/gh login, and (for Tier 2) real Azure resources.
Tools invoked: git CLI, gh CLI, cli-interactive-tester MCP tools (list_scenarios,
load_scenario, run_pre_hooks, start_session, send_action, finish_session,
run_post_hooks), the foundry-extension-scenario-worker agent, and ask_user.
This skill is the opt-in, run-locally flow a PR submitter uses to check their change for regressions. It:
- Resolves the current branch's PR link.
- Maps the PR's changed files to the impacted scenario tag set (
cmd:*/tier:*). - Enumerates and drives only the impacted scenarios through the tester.
- Posts a per-scenario results comment back on the PR.
It is cost- and side-effect-aware: Tier 0 is free/offline, Tier 1 needs Azure auth but
provisions nothing, Tier 1b (verify-deploy) provisions per-scenario Azure resources to
verify Tier 1 scaffolds actually deploy, and Tier 2 incurs Azure cost for cloud-feature
testing — both Tier 1b and Tier 2 are only run after explicit user confirmation.
This skill selects what to run (PR impact → tags) and owns the PR reporting. It does not
re-document how a scenario is driven — that is the executor spec at
cli/azd/extensions/azure.ai.agents/tests/cli-interactive-tester-scenarios/driving-mechanics.md,
which the spawned foundry-extension-scenario-worker agent follows for each scenario. This skill is the
selection-strategy half of the foundry-extension-scenario-orchestrator front door; the orchestrator may
dispatch it, or it may trigger directly.
What ships with it
4 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.
- 1mo ago Changed · +2 lines · -63 tokens per session 64b3e00b9e74
- 1mo ago First seen · 101 lines · 294 tokens per session scan A ac5d40bdb821
foundry-extension-scenario-pr-regression is a skill published in the GitHub repository Azure/azure-dev (570 stars, last pushed today), licensed MIT. It adds 231 tokens to every session and 1,402 once invoked, about $0.0009 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-10.
Other skills, from other repositories
azure-microsoft-playwright-testing-ts
Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.
agent-browser
Use the host-side agent-browser CLI for local browser smoke tests, screenshots, snapshots, and simple UI validation against forwarded localhost URLs.
browser-qa
Testing web apps through a real browser: reconnaissance before acting, selector discovery, state capture, console errors and screenshot evidence. Use on a web surface end to end, or to reproduce a front-end bug.
hatch3r-browser-verify
Opt-in browser verification skill — spec-run-first Playwright verification (assertions execute in the runner, agent reads only failures), axe-core a11y audits, toHaveScreenshot() regression diffs, E2E test scaffolds, and snapshot-mode exploratory driving. Default ON for UI-affecting agent invocations; disable globally…
hatch3r-qa-path
Produces a human-run manual QA test path from a PR, branch diff, or uncommitted working tree — a risk-ordered table of steps, expected results, and automated-coverage references plus a shippability sign-off. Rows are auto-proven via delegated verification sub-agents before emission, so the human walks only what…
hatch3r-a11y-audit
Runs a WCAG AA accessibility audit with findings and fixes across 7 scan categories (keyboard, contrast, ARIA, reduced motion, screen reader, high contrast, automated axe). Use when auditing and remediating accessibility.