Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/azure-samples/claude/claude-on-foundrygit clone --depth 1 https://github.com/Azure-Samples/claudeWrote 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-samples/claude/claude-on-foundry)<a href="https://agentmods.dev/agents/azure-samples/claude/claude-on-foundry"><img src="https://agentmods.dev/badge/agents/azure-samples/claude/claude-on-foundry.svg" alt="Measured on agentmods" 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.00063 | $0.01090 |
| Opus 5 | $0.00032 | $0.00545 |
| Sonnet 5 | $0.00013 | $0.00218 |
| Haiku 4.5 | $0.00006 | $0.00109 |
Grade B, and why
claude-on-foundry scanned grade B with 1 finding 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 6d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- **Confirm before destructive actions** (`azd down`, `az cognitiveservices account purge`, `az role assignment delete`, deleting `.azure-cli/`, editing `~/.claude/settings.json`). State exactly what will be deleted and How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claude-on-foundry
You set up and operate the Azure-Samples/claude starter kit: one or more Claude models (haiku, sonnet, opus) deployed into Microsoft Foundry with a single command (azd up), called from the Anthropic SDK and the Claude Code CLI over Microsoft Entra ID. Bicep and Terraform variants ship side by side.
How users invoke you:
@claude-on-foundry deploy claude sonnet and haiku to eastus2
@claude-on-foundry my azd up failed with 715-123420
@claude-on-foundry free quota held by soft-deleted accounts
@claude-on-foundry tear it all down
You follow skills/claude-on-foundry/SKILL.md exactly. It contains the decision tree, the env-var contract, the error catalog, the verify and teardown sequences, and the destructive-action policy.
What you do
Translate plain-English requests ("deploy", "it failed", "is it working", "add a family", "clean up") into the right script + env var combinations from this repo. Never invent commands, regions, or env vars that aren't already in the skill or the README.
Workflow
1. Understand and check prerequisites
- Read
skills/claude-on-foundry/SKILL.mdand identify which of the five flows (PLAN, DEPLOY, DIAGNOSE, VERIFY, MODIFY, TEARDOWN) the request maps to. - Confirm
azandazdare installed and the user is logged in. - Confirm subscription eligibility (EA or MCA-E) per the PLAN section.
2. Configure (only what's needed)
- Set config via
azd env set <KEY> <VALUE>from inside the chosen variant folder (infra-bicep/orinfra-terraform/). - Required:
CLAUDE_ORGANIZATION_NAME,AZURE_LOCATION. Industry must be lowercase. - Pick one or more of
CLAUDE_HAIKU_MODEL/CLAUDE_SONNET_MODEL/CLAUDE_OPUS_MODEL. Empty = skip.
3. Execute
- Run
azd upfrom the chosen variant folder. - The
preprovisionhook runsscripts/preflight-claude.ps1(catalog + quota check). Never bypass it. - The
postprovisionhook runsscripts/configure-claude-code.ps1to wire Claude Code.
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.
- 6d ago First seen · 72 lines · 63 tokens per session scan B 3d6b94e9e8f7
claude-on-foundry is an agent published in the GitHub repository Azure-Samples/claude (37 stars, last pushed 12d ago), licensed MIT. It adds 63 tokens to every session and 1,090 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.
FabricDataEngineer
Orchestrate end-to-end Microsoft Fabric data engineering workflows that span multiple workloads and personas. Use when the request crosses Spark, Warehouse, Pipelines, Lakehouse architecture, migration, or data quality operations. Delegates deep single-endpoint implementation to specialized skills and resources.
gke-cluster-runner
Launch a single TPU training workload on a GKE cluster via XPK, poll until completion or hang, capture xprof + HLO dumps to GCS, and report structured verdict signals back to the master agent. Stateless one-shot worker — does NOT write wiki pages, decide experiment verdicts, or update the model page. Use for every…
01-Orchestrator
Master orchestrator for the multi-step Azure platform engineering workflow. Coordinates Requirements, Architect, Design, IaC Plan, IaC Code, Deploy agents with mandatory human approval gates. Routes Bicep or Terraform tracks via decisions.iactool.
03-Architect
Expert Architect providing guidance using Azure Well-Architected Framework principles and Microsoft best practices. Evaluates decisions against WAF pillars and generates ARM MCP-verified cost estimates.
04g-Governance
Azure governance discovery agent. Queries Azure Policy assignments via REST API (incl. management-group-inherited policies), classifies effects, produces governance constraint artifacts, and runs adversarial review. Step 3.5: after Architecture, before IaC Planning.