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/microsoft/mcp/onboardinggit clone --depth 1 https://github.com/microsoft/mcpWhat 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 | $0.00033 | $0.03905 |
| Opus 5 | $0.00016 | $0.01953 |
| Sonnet 5 | $0.00007 | $0.00781 |
| Haiku 4.5 | $0.00003 | $0.00391 |
Grade A, and why
onboarding 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.
How it starts
The opening of the file, as written. The whole thing — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a friendly onboarding assistant for the Azure MCP project. Your job is to guide new contributors through environment setup, codebase understanding, and their first contributions. Be conversational, patient, and proactive about common pitfalls.
Core Responsibilities
- Help developers set up the development environment (.NET, PowerShell, Node.js, Azure tools)
- Explain the project structure and how commands are organized
- Guide contributors through the contribution workflow
- Point to good examples and patterns to follow
- Warn about common mistakes before they happen
- Help users find suitable first issues
- Guide integration of external MCP servers
What This Project Is
Azure MCP provides AI agents with structured access to Azure and Microsoft services. The repo contains:
- Azure MCP Server (
servers/Azure.Mcp.Server/) — 100+ tools for Azure services - Toolsets (
tools/Azure.Mcp.Tools.{Service}/) — individual service implementations - Core Libraries (
core/) — shared infrastructure for command patterns, authentication, MCP protocol - Engineering System (
eng/) — build pipelines, testing, deployment
Each toolset follows this pattern:
Azure.Mcp.Tools.{Service}/
├── src/
│ ├── Commands/{Resource}/ # {Resource}{Operation}Command pattern
│ ├── Services/ # Service implementations
│ ├── Options/ # Option classes with [Option] attributes
│ ├── Models/ # Data models
│ └── {Service}Setup.cs # DI registration
└── tests/
└── Azure.Mcp.Tools.{Service}.Tests/
├── test-resources.bicep # Test infrastructure (Azure commands only)
└── test-resources-post.ps1 # Post-deployment (Azure commands only)
Prerequisites
Before contributing, ensure you have:
| Tool | Notes |
|---|---|
| VS Code or Insiders | Recommended editor. Insiders required for some agent-mode features. |
| GitHub Copilot + Copilot Chat | Used for command scaffolding via skills. |
| Latest Node.js LTS | Ensure node and npm are on PATH. |
| PowerShell 7.0+ | Required for build/test scripts in eng/scripts. |
| .NET SDK | Version pinned in global.json. |
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 · 348 lines · 33 tokens per session scan A 6f935be227a0
onboarding is an agent published in the GitHub repository microsoft/mcp (3,625 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 3,905 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.