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-samples/copilot-instructionsgit clone --depth 1 https://github.com/microsoft/Agent365-SamplesWhat 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.03602 | $0.03602 |
| Opus 5 | $0.01801 | $0.01801 |
| Sonnet 5 | $0.00720 | $0.00720 |
| Haiku 4.5 | $0.00360 | $0.00360 |
Grade A, and why
Agent365-Samples 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 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 — 415 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions for Agent365-dotnet
Code Review Rules
Rule 1: Check for "Kairo" Keyword
- Description: Scan code for any occurrence of the keyword "Kairo"
- Action: If "Kairo" is found in any code file:
- Flag it for review
- Suggest removal or replacement with appropriate terminology
- Check if it's a legacy reference that needs to be updated
- Files to check: All source files (
.cs,.csx,.py,.js,.ts,.mjs) in the repository
Rule 2: Verify Copyright Headers
- Description: Ensure all source code files have proper Microsoft copyright headers
- Action: If a source file is missing a copyright header:
- Add the Microsoft copyright header at the top of the file
- The header should be placed before any using/import statements or code
- Maintain proper formatting and spacing
- Use language-appropriate comment syntax
Required Copyright Header Format
C# Files (.cs, .csx):
// Copyright (c) Microsoft Corporation.
// Licensed under the MIT License.
Python Files (.py):
# Copyright (c) Microsoft Corporation.
# Licensed under the MIT License.
JavaScript/TypeScript Files (.js, .ts, .mjs):
// Copyright (c) Microsoft Corporation.
// Licensed under the MIT License.
Implementation Guidelines
When Reviewing Code:
-
Kairo Check:
- Search for case-insensitive matches of "Kairo"
- Review context to determine if it's:
- A class name
- A namespace
- A variable name
- A comment reference
- A using statement
- A string literal
- Suggest appropriate alternatives based on the context
-
Header Check:
- Verify the first non-empty lines of source files
- If missing, prepend the copyright header with appropriate comment syntax
- Ensure there's a blank line after the header before other content
- Do not add headers to:
- Auto-generated files:
- C#: Marked with
<auto-generated>or// <auto-generated />,.Designer.cs,.g.cs - Python: Files with auto-generated markers
- JavaScript/TypeScript:
.d.tstype definitions, files with@generatedmarker
- C#: Marked with
- Files with
#pragma warning disableat the top for generated code - Third-party/vendored code
- Auto-generated files:
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 · 415 lines · 3,602 tokens per session scan A c461443c9f64
Agent365-Samples copilot-instructions.md is an instructions file published in the GitHub repository microsoft/Agent365-Samples (105 stars, last pushed 29d ago), licensed MIT. It adds 3,602 tokens to every session, about $0.0180 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
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.
buildNext
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).
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.
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).
spec-kit 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
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.