verify-dotnet-samples

verify-dotnet-samples is a skill for Claude Code, Codex from microsoft/agent-framework. It costs 40 tokens per session (676 once invoked), scanned A, original, MIT.

A workflow for building, running, and checking suitable .NET sample projects in the Agent Framework repository.

In plain words
What is it for?
Use it to inspect sample code, check required environment variables, run supported samples, compare their output with expectations, and report samples that could not be run.
Why use it?
It shows whether samples actually work and explains differences between expected and produced output.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one.

Good fit Use it to inspect sample code, check required environment variables, run supported samples, compare their output with expectations, and report samples that could not be run.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/agent-framework/verify-dotnet-samples
About the project

Microsoft Agent Framework is a multi-language framework for building, coordinating, and running AI agents and workflows in Python and .NET. Teams use it for agent systems that need orchestration, collaboration, durability, observability, governance, or human involvement beyond a single prompt or chat loop. Catalogue add-ons provide skills and instructions for working with the framework.

microsoft/agent-framework · 14,148 stars · on GitHub · aka.ms

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/agent-framework --skill verify-dotnet-samples
Clone the repo
git clone --depth 1 https://github.com/microsoft/agent-framework

Made for: Claude Code, Codex.

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 verify-dotnet-samples

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/agent-framework/verify-dotnet-samples"><img src="https://agentmods.dev/badge/skills/microsoft/agent-framework/verify-dotnet-samples.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 676 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. Third-party audits
  • Snyk pass 7 Sept 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00040 $0.00676
Opus 5.5 $0.00016 $0.00270
Sonnet 5.5 $0.00008 $0.00135
Haiku 4.5 $0.00004 $0.00068

Measured 1mo ago against content hash 71a4309ff9b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

verify-dotnet-samples 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.

dotnet/.github/skills/verify-dotnet-samples/SKILL.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Verifying .NET Sample Projects

Sample Pre-requisites

We should only support verifying samples that:

  1. Use environment variables for configuration.
  2. Have no complex setup requirements, e.g., where multiple applications need to be run together, or where we need to launch a browser, etc.

Always report to the user which samples were run and which were not, and why.

Verifying a sample

Samples should be verified to ensure that they actually work as intended and that their output matches what is expected. For each sample that is run, output should be produced that shows the result and explains the reasoning about what output was expected, what was produced, and why it didn't match what the sample was expected to produce.

Steps to verify a sample:

  1. Read the code for the sample
  2. Check what environment variables are required for the sample
  3. Check if each environment variable has been set
  4. If there are any missing, give the user a list of missing environment variables to set and terminate
  5. Summarize what the expected output of the sample should be
  6. Run the sample
  7. Show the user any output from the sample run as it gets produced, so that they can see the run progress
  8. Check the output of the run against expectations
  9. After running all requested samples, produce output for each sample that was verified:
  10. If expectations were matched, output the following:
    [Sample Name] Succeeded
    
  11. If expectations were not matched, output the following:
    [Sample Name] Failed
    Actual Output:
    [What the sample produced]
    Expected Output:
    [Explanation of what was expected and why the actual output didn't match expectations]
    

Environment Variables

Most samples use environment variables to configure settings.

var endpoint = Environment.GetEnvironmentVariable("AZURE_OPENAI_ENDPOINT") ?? throw new InvalidOperationException("AZURE_OPENAI_ENDPOINT is not set.");
var deploymentName = Environment.GetEnvironmentVariable("AZURE_OPENAI_DEPLOYMENT_NAME") ?? "gpt-4o-mini";

Read the full file on GitHub · 83 lines

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. 1mo ago First seen · 83 lines · 40 tokens per session scan A 71a4309ff9b8

Subscribe to this mod's changes

verify-dotnet-samples is a skill published in the GitHub repository microsoft/agent-framework (14,148 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 676 once invoked, about $0.0002 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-08-30.

Related

Other skills, from other repositories

nw-fp-fsharp

F# language-specific patterns, Railway-Oriented Programming, and Computation Expressions.

nWave-ai/nWave · 21 tokens

qa-testing-nunit

Designs NUnit-based C# test suites for API, component, and integration coverage. Use when creating fixtures, wiring Testcontainers, or reducing flaky CI behavior.

vasilyu1983/AI-Agents-public · 37 tokens

rn-testing

This skill should be used when the user asks to "write a Maestro test", "create E2E flows", "add testIDs", "run UI tests", "run E2E tests", "verify a feature works", "test my screen", "set up maestro-runner", "mock network requests", "inspect store state", "write test assertions", or needs guidance on test timing…

Lykhoyda/rn-dev-agent · 106 tokens

capturing-proof

This skill should be used when the user asks to "capture proof", "record a demo of this feature", "make a video showing it works", "record the flow for the PR", "generate a PR body", "capture screenshots for the PR", "proof-capture", or when a verified feature needs PR-ready proof artifacts (video + numbered…

Lykhoyda/rn-dev-agent · 105 tokens

agents-md-checker

Checks which instruction files (AGENTS.md, CLAUDE.md, GEMINI.md, Cursor rules, Copilot instructions) each coding agent loads from a repo, what gets cut or skipped, and whether the commands those files document still work. Use when the user asks whether Claude Code, Codex, Gemini CLI, Cursor, OpenCode, Copilot, or…

RyanAlberts/best-of-Agent-Harnesses · 158 tokens

harness-test-drive

Test-drives coding agents (Claude Code, Codex, Gemini CLI) on tasks mined from the user's own git history: each agent gets a past commit message in a fresh copy of the repo, and the repo's own tests score how many tasks it completes, dollars per task, minutes, and change size. Use when the user asks which coding agent…

RyanAlberts/best-of-Agent-Harnesses · 153 tokens