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 instructions/microsoft/agent365-dotnet/claude-mdgit clone --depth 1 https://github.com/microsoft/Agent365-dotnetWhat 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.02322 | $0.02322 |
| Opus 5 | $0.01161 | $0.01161 |
| Sonnet 5 | $0.00464 | $0.00464 |
| Haiku 4.5 | $0.00232 | $0.00232 |
Grade A, and why
Agent365-dotnet CLAUDE.md 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.
How it starts
The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Build Commands
Basic Build Operations
# Build the entire solution
dotnet build src/Microsoft.Agents.A365.Sdk.sln
# Build using PowerShell script (recommended)
./build/build.ps1
# Full clean rebuild
./build/build.ps1 -Clean -Restore
# Build with tests
./build/build.ps1 -Test
# Build with NuGet packaging
./build/build.ps1 -Pack
# Debug build with tests
./build/build.ps1 -Configuration Debug -Test
Testing
# Run all tests
dotnet test src/Microsoft.Agents.A365.Sdk.sln
# Run tests using build script
./build/build.ps1 -Test
# Run tests for a specific project
dotnet test src/Tests/Runtime.Tests/Microsoft.Agents.A365.Runtime.Tests.csproj
Package Management
- All package versions are centralized in
src/Directory.Packages.props - To add a new package: add the version to
Directory.Packages.props, then reference without version in the.csproj - Never specify versions directly in project files
Code Standards
Copyright Headers
Every C# file must include this header at the top:
// Copyright (c) Microsoft Corporation.
// Licensed under the MIT License.
Exceptions:
- Auto-generated files (
.g.cs,.designer.cs, files with<auto-generated>markers) - Files in
bin/,obj/directories - Third-party or vendored code
Legacy References
- Never use the keyword "Kairo" in any code - this is legacy terminology that must be replaced
Observability Export Configuration — Coordinated Review Required
The following three constants must stay in sync. If a PR changes any one of them, the reviewer (human or Copilot) must ask the author to confirm the other two are still correct:
| Constant | Location |
|---|---|
ProdObservabilityScope |
src/Observability/Runtime/Common/EnvironmentUtils.cs (accessed via GetObservabilityAuthenticationScope()) |
DefaultEndpointHost |
src/Observability/Runtime/Tracing/Exporters/Agent365ExporterOptions.cs |
| Export URL path pattern | BuildEndpointPath() in src/Observability/Runtime/Tracing/Exporters/Agent365ExporterCore.cs |
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.
- 2d ago First seen · 247 lines · 2,322 tokens per session scan A 17b8ee92432b
Agent365-dotnet CLAUDE.md is an instructions file published in the GitHub repository microsoft/Agent365-dotnet (29 stars, last pushed 1mo ago), licensed MIT. It adds 2,322 tokens to every session, about $0.0116 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 instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.