Microsoft Build 2026 DEM341 is a demo repository showing how multi-agent applications can emit consistent OpenTelemetry GenAI traces across different frameworks and cloud environments. It is for learning how to observe agent routing and latency and evaluate agent behavior through Microsoft Foundry. The catalogue instructions support working through the demo and its sample code.
Borrowing it
Nothing to install: this file belongs to microsoft/Build26-DEM341-any-agent-any-cloud-standardized-tracing-with-foundry-and-opentelemetry. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/Build26-DEM341-any-agent-any-cloud-standardized-tracing-with-foundry-and-opentelemetry/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/microsoft/Build26-DEM341-any-agent-any-cloud-standardized-tracing-with-foundry-and-opentelemetryWrote 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.
[](https://agentmods.dev/instructions/microsoft/build26-dem341-any-agent-any-cloud-standardized-tracing-with-foundry-and-opentelemetry/copilot-instructions)<a href="https://agentmods.dev/instructions/microsoft/build26-dem341-any-agent-any-cloud-standardized-tracing-with-foundry-and-opentelemetry/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/microsoft/build26-dem341-any-agent-any-cloud-standardized-tracing-with-foundry-and-opentelemetry/copilot-instructions/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.
<a href="https://agentmods.dev/instructions/microsoft/build26-dem341-any-agent-any-cloud-standardized-tracing-with-foundry-and-opentelemetry/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/microsoft/build26-dem341-any-agent-any-cloud-standardized-tracing-with-foundry-and-opentelemetry/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00469 | $0.00469 |
| Opus 5 | $0.00234 | $0.00234 |
| Sonnet 5 | $0.00094 | $0.00094 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
Build26-DEM341-any-agent-any-cloud-standardized-tracing-with-foundry-and-opentelemetry copilot-instructions.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 12d 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.
Copies of this mod
6 near-identical copies found in the catalogue:
- Build26-DEM332-from-zero-to-teammate-in-25-minutes-build-a-teams-agent-live copilot-instructions.md — 100% identical, 0 lines differ
- Build26-BRK241-from-prototype-to-production-build-and-run-agents-at-scale copilot-instructions.md — 100% identical, 0 lines differ
- Build26-BRK228-modern-resiliency-from-build-to-recovery-through-agentic-ai copilot-instructions.md — 100% identical, 0 lines differ
- Build26-DEM312-multi-agents-in-action-with-3-ai-agents-3-frameworks-tools-models copilot-instructions.md — 100% identical, 0 lines differ
- Build26-DEM364-simplify-app-dev-with-cloud-native-postgresql-in-azure-horizondb copilot-instructions.md — 94% identical, 2 lines differ
- Build26-DEM351-ai-skills-navigator-accelerate-tech-skills-with-personalized-learning copilot-instructions.md — 94% identical, 2 lines differ
What it actually says
This is a Microsoft Build 2026 session content repository.
If GUIDANCE.md exists in this repo, the repo has not yet been fully set up. When a content creator asks for help preparing the repo, read GUIDANCE.md and follow its instructions. The setup uses a three-phase model:
- Get Started — Session identity, learning outcomes, technologies, content owners
- Refine Content — Organize session content into /docs/ and /src/, fill in Getting Started sections (can be run multiple times as content evolves)
- Finalize — Final review, repo settings, slides/recordings links, delete GUIDANCE.md
When the creator asks for help, determine which phase they want to work on. You can detect this based on what's already filled in:
- If the README still has placeholder text (BRKXXX, "Add Session Description"), start with Get Started
- If the README has session info but content isn't organized yet, suggest Refine Content
- If content is organized and they want to finalize, suggest Finalize
Key constraints:
- Never commit secrets, API keys, or credentials. Use environment variables.
- Do not modify LICENSE, LICENSE-DOCS, CODE_OF_CONDUCT.md, or SECURITY.md.
- Do not add large binary files (PowerPoint, video, recordings) to the repo. Links are fine.
- The
_remove-before-publish/folder is for source materials (abstracts, screenshots, notes). Its contents are gitignored — scan it for context but never try to commit files from it. Direct creators to put reference materials there, not in the repo root. - Use the Microsoft Learn MCP Server (configured in .vscode/mcp.json) to find relevant learn.microsoft.com links when populating resource sections.
Issue Support
If a user asks for help filing an issue, or reports a problem:
- Check
.github/ISSUE_TEMPLATE/to discover available issue templates - If templates exist, match the user's request to the best-fit template and walk them through the fields
- If no templates exist, create a plain issue with a clear title and description
- Check
gh label listfor available labels and apply relevant ones - Do not hardcode template names or labels — always discover what's available at runtime
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.
- 12d ago First seen · 28 lines · 469 tokens per session scan A 2b0e816d3009
Build26-DEM341-any-agent-any-cloud-standardized-tracing-with-foundry-and-opentelemetry copilot-instructions.md is an instructions file published in the GitHub repository microsoft/Build26-DEM341-any-agent-any-cloud-standardized-tracing-with-foundry-and-opentelemetry (11 stars, last pushed 23d ago), licensed MIT. It adds 469 tokens to every session, about $0.0023 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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.
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).