validate-microsoft-foundry-hosted-agent

validate-microsoft-foundry-hosted-agent is a skill for Claude Code from microsoft/foundry-dev-tools. It costs 47 tokens per session (191 once invoked), scanned A, original, MIT.

A validation workflow for Microsoft Foundry hosted-agent projects, followed by opening the resulting validation report.

In plain words
What is it for?
It is for validating a Microsoft Foundry hosted agent when a user explicitly requests that check.
Why use it?
It checks a hosted-agent project against Microsoft Foundry's recommended practices and makes the report available for inspection.

Skill for Claude Code ✓ vendor

Written for Claude Code: user-invocable in frontmatter.

Good fit It is for validating a Microsoft Foundry hosted agent when a user explicitly requests that check.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/foundry-dev-tools/validate-microsoft-foundry-hosted-agent
About the project

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.

microsoft/foundry-dev-tools · 2,052 stars · on GitHub · microsoft.github.io

Install

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.

Any agent
npx skills add microsoft/foundry-dev-tools --skill validate-microsoft-foundry-hosted-agent
Clone the repo
git clone --depth 1 https://github.com/microsoft/foundry-dev-tools

Made for: Claude Code.

Wrote 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.

agentmods badge for validate-microsoft-foundry-hosted-agent

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/foundry-dev-tools/validate-microsoft-foundry-hosted-agent/github.svg)](https://agentmods.dev/skills/microsoft/foundry-dev-tools/validate-microsoft-foundry-hosted-agent)
Your own site
<a href="https://agentmods.dev/skills/microsoft/foundry-dev-tools/validate-microsoft-foundry-hosted-agent"><img src="https://agentmods.dev/badge/skills/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.

agentmods 80×15 button for validate-microsoft-foundry-hosted-agent

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/foundry-dev-tools/validate-microsoft-foundry-hosted-agent"><img src="https://agentmods.dev/badge/skills/microsoft/foundry-dev-tools/validate-microsoft-foundry-hosted-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 191 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.00191
Opus 5 $0.00023 $0.00096
Sonnet 5 $0.00009 $0.00038
Haiku 4.5 $0.00005 $0.00019

Measured 2d ago against content hash a957845d27bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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 2d 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.

microsoft-foundry/skills/validate-microsoft-foundry-hosted-agent/SKILL.md · 25 lines

What it actually says

Validate a Microsoft Foundry hosted agent

Load the microsoft-foundry skill and follow foundry-agent/validate/validate.md exactly. Treat the slash-command input as free-form validation input.

After the canonical validation workflow writes its JSON report, open the hosted-agent-validation-report canvas with:

{
  "report": "<absolute or workspace-relative JSON report path>"
}

Use a stable canvas instance ID derived from the report ID. Do not transform the report before opening the canvas.

Changes

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.

  1. 2d ago First seen · 25 lines · 47 tokens per session scan A a957845d27bf

Subscribe to this mod's changes

validate-microsoft-foundry-hosted-agent is a skill published in the GitHub repository microsoft/foundry-dev-tools (2,052 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 191 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-09-08.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens