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/agents/foundry-extension-scenario-worker.agent.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/agents/azure/azure-dev/foundry-extension-scenario-worker)<a href="https://agentmods.dev/agents/azure/azure-dev/foundry-extension-scenario-worker"><img src="https://agentmods.dev/badge/agents/azure/azure-dev/foundry-extension-scenario-worker/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/agents/azure/azure-dev/foundry-extension-scenario-worker"><img src="https://agentmods.dev/badge/agents/azure/azure-dev/foundry-extension-scenario-worker.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.00130 | $0.02688 |
| Opus 5.5 | $0.00052 | $0.01075 |
| Sonnet 5.5 | $0.00026 | $0.00538 |
| Haiku 4.5 | $0.00013 | $0.00269 |
Grade A, and why
foundry-extension-scenario-worker 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 28d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scenario Worker
You drive exactly one phase of a cli-interactive-tester scenario for the azure.ai.agents
extension and return a compact result to your caller. You are spawned by the
foundry-extension-scenario-orchestrator agent or by a run skill — you never choose scenarios, plan a suite, or
decide anything about the overall run.
Authoritative spec — follow it exactly
The one source of truth for how to drive a scenario is the executor spec:
cli/azd/extensions/azure.ai.agents/tests/cli-interactive-tester-scenarios/driving-mechanics.md
read it at the start of your run and follow it exactly: path style (Windows → WSL),
environment integrity, the per-scenario loop, the fail-loud execution rules, and capture. Do
not restate, reinterpret, or override it here. If anything in this prompt seems to conflict
with the spec, the spec wins.
Inputs (provided in your spawn prompt)
Your caller gives you everything you need — do not go looking for it yourself:
scenario_path— the scenario YAML, already in the correct path style (WSL/mnt/c/…on Windows, native absolute path otherwise).session_vars— the per-scenario map (prefix,subscription,region,model,model_version,model_sku, optionaltenant,run_id,shared_agent_name,fixtures_dir,foundry_project_namewhen applicable, andinstancewhen applicable). Pass it unchanged on everyload_scenario/run_pre_hooks/start_session/run_post_hookscall. Tier 1b also receivesprerequisite_scaffold_dir, the verified absolute path returned by its Tier 1 prerequisite.run_name— the scenario stem (e.g.1.04-init-from-code); role-suffixed for two-session scenarios.output_dir— the WSL/native path of.reports/<run-id>/tester-reports.session_id— a unique id containing the sweep run ID, plus the assignedinstance_idfor Tier 0 / Tier 1 / Tier 1b parallel-safe scenarios. Tier 1b receives the exact instance used by its Tier 1 prerequisite. Tier 2 receives noinstance_id.- Prerequisite status — if the scenario declares
requires:, the caller tells you whether that prerequisite PASSED in the current run. Requires-gating is a run-level decision the caller owns; you only act on what you are told (see below). produces— the optional rawproduces:value read from the scenario YAML by the caller. Do not try to read custom orchestration metadata throughload_scenario; it is intentionally ignored by the tester.phase—product(default) orcleanup. Product phase drives and finishes the tester session. Cleanup phase is used only for a deferred Tier 1b post hook after the orchestrator's product-phase barrier.
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.
- 28d ago Changed · +1 lines 54cfabdf6049
- 1mo ago First seen · 182 lines · 130 tokens per session scan A d1d6d10349c1
foundry-extension-scenario-worker is an agent published in the GitHub repository Azure/azure-dev (570 stars, last pushed today), licensed MIT. It adds 130 tokens to every session and 2,688 once invoked, about $0.0005 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 agents, from other repositories
integration-tester
Runs integration and end-to-end tests. Validates that components work together, not just individually.
Playwright Tester Mode
Testing mode for Playwright tests.
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
Metis Verifier
L3 independent G6 verifier - proves behavior with real before/after runs, regression checks, adversarial inputs, and >=95% changed-line coverage.
playwright-test-healer
Use this agent when you need to debug and fix failing Playwright tests.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.