project-structure

A guide to the folders and projects in the Agent Framework .NET codebase. It explains where source code, tests, sample applications, and shared or legacy code are kept.

In plain words
What is it for?
Use it when navigating the .NET solution, locating a provider or workflow package, finding its unit or integration tests, or looking for sample applications.
Why use it?
It helps developers find the right project without searching through the whole repository or guessing what each folder contains.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/microsoft/agent-framework/project-structure
Any agent
npx skills add microsoft/agent-framework --skill project-structure
Clone the repo
git clone --depth 1 https://github.com/microsoft/agent-framework

Made for: Claude Code, Codex.

Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 369 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00016 $0.00369
Opus 5 $0.00008 $0.00185
Sonnet 5 $0.00003 $0.00074
Haiku 4.5 $0.00002 $0.00037

Measured yesterday against content hash c04ca47f9a2f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

project-structure 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.

dotnet/.github/skills/project-structure/SKILL.md · 32 lines

What it actually says

Agent Framework .NET Project Structure

dotnet/
├── src/
│   ├── Microsoft.Agents.AI/                      # Core AI agent implementations
│   ├── Microsoft.Agents.AI.Abstractions/         # Core AI agent abstractions
│   ├── Microsoft.Agents.AI.A2A/                  # Agent-to-Agent (A2A) provider
│   ├── Microsoft.Agents.AI.OpenAI/               # OpenAI provider
│   ├── Microsoft.Agents.AI.Foundry/               # Microsoft Foundry Agents (v2) provider
│   ├── Microsoft.Agents.AI.AzureAI.Persistent/   # Legacy Microsoft Foundry Agents (v1) provider
│   ├── Microsoft.Agents.AI.Anthropic/            # Anthropic provider
│   ├── Microsoft.Agents.AI.Workflows/            # Workflow orchestration
│   └── ...                                       # Other packages
├── samples/                                      # Sample applications
└── tests/                                        # Unit and integration tests

Main Folders

Folder Contents
src/ Source code projects
tests/ Test projects — named <Source-Code-Project>.UnitTests or <Source-Code-Project>.IntegrationTests
samples/ Sample projects
src/Shared, src/LegacySupport Shared code files included by multiple source code projects (see README.md files in these folders or their subdirectories for instructions on how to include them in a project)
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. yesterday First seen · 32 lines · 16 tokens per session scan A c04ca47f9a2f

Subscribe to this mod's changes

project-structure is a skill published in the GitHub repository microsoft/agent-framework (13,222 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 369 once invoked, about $0.0001 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-08-30.

Related

Other skills, from other repositories

swarmclaw

AI agent runtime and multi-agent orchestration platform. Teaches agents how to use SwarmClaw's 6 primitive tools, persistent memory, dreaming, delegation, connectors, credentials, and the skill system. Use when an agent is running on SwarmClaw and needs to understand the platform's capabilities.

swarmclawai/swarmclaw · 67 tokens

agent-collaboration

Use this skill when coordinating multiple AI agents. Covers multi-agent patterns, handoffs, and orchestration strategies.

ApexIQ/skillsmith · 27 tokens

crewai-multi-agent

Multi-agent orchestration framework for autonomous AI collaboration. Use when building teams of specialized agents working together on complex tasks, when you need role-based agent collaboration with memory, or for production workflows requiring sequential/hierarchical execution. Built without LangChain dependencies…

davila7/claude-code-templates · 61 tokens

strands-review

Local preview of the strands-agents/devtools /strands review agent. Body is the upstream Task Reviewer SOP verbatim — do not paraphrase. Use when the user types /strands-review, asks for a "strands review" of a PR, or wants to anticipate what the remote /strands review GitHub Action will flag. Findings are close but…

strands-agents/harness-sdk · 125 tokens

docs-writer

Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X"…

strands-agents/harness-sdk · 74 tokens

pr-writer

Generates pull request titles and descriptions. Use when the user asks to create, open, write, draft, or generate a PR, pull request, or merge request description.

strands-agents/harness-sdk · 39 tokens