Microsoft Foundry DevTools is a collection of developer tools, documentation, community resources, and source code for building, deploying, evaluating, and managing AI applications and agents with Microsoft Foundry. Developers use its terminal tools, coding-agent guidance, VS Code toolkit, and Foundry Canvas to choose a development workflow. The catalogue includes a Foundry skill that gives coding agents reusable guidance for working with Foundry.
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.
git clone --depth 1 https://github.com/microsoft/foundry-dev-toolsWrote 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/microsoft/foundry-dev-tools/validate-microsoft-foundry-hosted-agent)<a href="https://agentmods.dev/commands/microsoft/foundry-dev-tools/validate-microsoft-foundry-hosted-agent"><img src="https://agentmods.dev/badge/commands/microsoft/foundry-dev-tools/validate-microsoft-foundry-hosted-agent/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/microsoft/foundry-dev-tools/validate-microsoft-foundry-hosted-agent"><img src="https://agentmods.dev/badge/commands/microsoft/foundry-dev-tools/validate-microsoft-foundry-hosted-agent.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.00019 | $0.00286 |
| Opus 5.5 | $0.00008 | $0.00114 |
| Sonnet 5.5 | $0.00004 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
validate-microsoft-foundry-hosted-agent 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 yesterday.
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
Validate a Microsoft Foundry hosted agent
Treat the slash-command input as free-form validation input:
-
Use its
agentPath, or the current working directory when none is supplied. PreserverulesFileand other input. -
Load the
microsoft-foundryskill and followfoundry-agent/validate/validate.md. PassagentPathas the only target context; the canonical workflow selects and validates one hosted agent. -
If the workflow returns
no-hosted-agent, ask once for a direct path and retry. Stop if the user provides no path or the retry finds no agent. -
When the workflow returns a JSON/Markdown report pair, open exactly one
agent-buildercanvas (Microsoft Foundry) with the returned JSON path in its validation report view. Pass this object asopen_canvas'sinput:{ "view": "validation-report", "report": "<absolute or workspace-relative JSON report path>" } -
Derive a stable instance ID from the report path. Use only alphanumeric characters,
.,_, or-; start with an alphanumeric character; and limit it to 128 characters. -
Do not open a canvas without a report pair.
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.
- yesterday First seen · 23 lines · 19 tokens per session scan A 503a54dc505d
validate-microsoft-foundry-hosted-agent is a command published in the GitHub repository microsoft/foundry-dev-tools (2,054 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 286 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-11-06.
validate-microsoft-foundry-hosted-agent compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| validate-microsoft-foundry-hosted-agentmicrosoft/foundry-dev-tools | Command | 2.1k | 2d ago | MIT | A | 19 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |