MicrosoftAGENTS.mdcopilot-sdk-samples / sdk
microsoft/copilot-sdk-samples/samples/skill-testing/sdk/AGENTS.md
Sample-specific guidance for AI agents. Use verbose: true in harness config for detailed test output.
AGENTS.md examples from real projects
How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Worked for most · soon
MicrosoftAGENTS.mdMicrosoftAGENTS.mdcopilot-sdk-samples / sdk
microsoft/copilot-sdk-samples/samples/teams/sdk/AGENTS.md
Sample-specific guidance for AI agents. Mock connector simulates Teams workspace with teams, channels, and users.
MicrosoftAGENTS.mdHosted_Agents_Workshop_dotNET
microsoft/Hosted_Agents_Workshop_dotNET/AGENTS.md
This file defines repository-level guidance for coding agents and contributors. This repo is a beginner workshop for Microsoft Foundry hosted agents with .NET 10. Primary learning flow: When UI images need refresh for docs: Expected outputs: Before publishing updates:
MicrosoftAGENTS.mdmicrosoft-copilot-agents-playbook / Chef-Agent-Initial
microsoft/microsoft-copilot-agents-playbook/04-evaluate/demo-chef-agent/Chef-Agent-Initial/AGENTS.md
This is an M365 Copilot declarative agent project managed by the ATK CLI. When working on this project, you MUST use the appropriate skill for the task. Do NOT work directly on files without invoking a skill first. This is a declarative agent project. For ANY task in this workspace — regardless of what it is — you MUST invoke the declarative-agent-developer skill BEFORE doing any work. This is not optional. Do not attempt to handle any task yourself. Always…
MicrosoftAGENTS.mdFSQ
microsoft/FSQ/AGENTS.md
This repository uses Spec-Driven Development for project development. Root SPEC.md and relevant module SPEC.md files are the grounding truth for project code and project logic. They do not define the SDD workflow. This file and .github/skills/ control agent write authorization and SDD phase transitions. Project SPEC.md files must not duplicate or override those workflow rules. Ordinary discussion, explanation, review, and planning are read-only. Do not automatically load or invoke repository workflow skills. Before creating, modifying, renaming, or deleting project development…
MicrosoftAGENTS.mdFSQ / codex
microsoft/FSQ/fsq_agent/resources/codex/AGENTS.md
This project uses two Codex custom agents under .codex/agents/: This template is installed in the FSQ-managed block of the project-root AGENTS.md. The TOML files define the child agents; the parent owns when to use each one. Preserve all project instructions outside the managed block. The Codex project and intended FSQ Workspace may be different directories. Workspace-scoped commands must run from the exact registered root shown above. When the user asks to run an FSQ UI test, create a Case, replay…
MicrosoftAGENTS.mdValueLens-for-Microsoft-Copilot / Fabric App
microsoft/ValueLens-for-Microsoft-Copilot/1. Fabric/Fabric App/AGENTS.md
You will help the user build out this React-based web app that visualizes data from Power BI semantic models. The app fetches live data via DAX queries, renders charts and grids using Vega-Lite and a built-in DataGrid component, and supports light/dark theming. Your job is to discover the user's data, write correct DAX queries, build React components that fetch and display that data, and validate the result in the browser. Break tasks into independent pieces and delegate them to sub-agents…
MicrosoftAGENTS.mdDocAtlas-Harness / web
microsoft/DocAtlas-Harness/web/AGENTS.md
These rules apply to the independent web/ application in the official Harness integration checkout. Its TypeScript Core lives in packages/core/; Python is the local document sidecar. The original repository-root Python CLI/package/lock is independent and must not change as a side effect of Web work. Original video and sibling research checkouts, and every .sources/ checkout, are read-only inputs unless the user explicitly requests changes there. Historical DSH rules below describe compatibility boundaries, not a requirement to import that host. migration-source.json preserves…
MicrosoftAGENTS.mdlearn-ai-native-dev
microsoft/learn-ai-native-dev/AGENTS.md
This file provides context and guidelines for AI agents (GitHub Copilot, Claude, etc.) working on this codebase. Two surfaces, two homes. docs/ is the design spec for the website-as-product (what we teach, how content is structured, principles). .github/ is the build harness (instructions, prompt files, skills, custom agents, hooks) for editing the website. Start with docs/README.md and docs/harness.md. AI-Native Development Tutorial Website - An interactive tutorial teaching anyone how to accelerate their workflow using AI-Native development techniques. Teach developers —…
MicrosoftAGENTS.mdMigrate2GSA
microsoft/Migrate2GSA/AGENTS.md
PowerShell module and tooling to migrate third-party SSE/ZTNA configurations to Microsoft Entra Global Secure Access (Private Access / Internet Access). This file is the entry point for humans and coding agents. verify.ps1 validates the module manifest (Test-ModuleManifest), imports the module, and runs Pester tests if present. A change is done when verify.ps1 passes, the pre-commit hook (.githooks/pre-commit.ps1) is satisfied, and docs are updated for user-facing changes.
MicrosoftAGENTS.mdSharePoint-Embedded-VS-Code-Extension
microsoft/SharePoint-Embedded-VS-Code-Extension/AGENTS.md
This repository is a VS Code extension for managing SharePoint Embedded resources. Its primary surfaces are the extension host under src/, the Storage Explorer React webview under webview-ui/, and Playwright coverage under ui-tests/. These instructions apply to every automated or interactive coding agent working in this repository. More specific instructions may narrow this authority, but must not weaken the safety rules below. Machine-readable worker contracts, role definitions, and authority policies live under .agent/. See .agent/README.md before running a contracted task.
MicrosoftAGENTS.mdagentic-sdlc-starter
microsoft/agentic-sdlc-starter/AGENTS.md
No summary in the file. Open it to read it.
MicrosoftAGENTS.mdamplifier-app-cli
microsoft/amplifier-app-cli/AGENTS.md
Directory commands persist write policy under tool-filesystem. During config resolution, project only its operator write grants and denies onto declared tool-apply-patch entries; never copy bundle filesystem defaults, read policy, source, or engine. Validate both shared lists before granting anything. Preserve explicit empty patch allowlists and the module's omitted-policy default scope. Shared filesystem denied_write_paths: null means no additional denies, matching that consumer; preserve it without forwarding null or clearing patch denies. Append grants to the portable additional_allowed_write_paths field, not allowed_write_paths; union…
MicrosoftAGENTS.mdWinAppVSCE / vsce-testing
microsoft/WinAppVSCE/.github/skills/vsce-testing/AGENTS.md
Read this first. It is the onboarding contract for any agent/session working in vsce-testing. It encodes the validated way to drive the WinApp VS Code extension (microsoft-winappcli.winapp) inside a live VS Code instance, plus every gotcha that has already cost hours to rediscover. Follow the "Getting started" checklist before doing anything else. This directory lives inside the WinAppVSCE repo at .github/skills/vsce-testing/. It provides the infrastructure for an agent to launch an isolated VS Code instance with the WinApp extension installed…
MicrosoftAGENTS.mdamplifier-foundation / mechanisms
microsoft/amplifier-foundation/context/understanding-mechanisms/mechanisms/agents.md
An agent is a specialist sub-agent that gets spawned as a child session via the delegate tool. Agents are markdown files with meta: YAML frontmatter (not bundle: frontmatter) that define a partial configuration overlay merged with the parent session's config when spawned. They exist primarily as "context sinks" -- absorbing heavy token costs in their own isolated context and returning only concise summaries. Agents ARE bundles structurally. The difference is conventional: - Bundles use bundle: frontmatter -- complete, ready-to-run configuration…
MicrosoftAGENTS.mdamplifier-foundation / libraries
microsoft/amplifier-foundation/libraries/AGENTS.md
Read this directory's README and the affected library's README, provenance and qualification notes before changing it. Own one library directory per worktree; coordinate shared CI/release files through an integration owner. - Keep packages independently installable. Do not add them to the base Foundation wheel, root imports or required dependencies merely because their sources live here. - Keep application policy, host/client authority and native execution outside. Public mechanisms take explicit storage paths and scoped inputs from callers. - Preserve native history…
MicrosoftAGENTS.mdPilotSwarm / home
microsoft/PilotSwarm/packages/sdk/examples/repo-workspaces/seed/home/AGENTS.md
This file is yours. Every session you start reads it, so change it to tell your sessions how you like to work. - Keep answers short. Lead with the answer. - Save anything a later session should find in this folder. The notes skill says how. - Put files you want other people to see in the shared folder: extra folder "shared", at /ws/shared.
MicrosoftAGENTS.mdcopilot-studio-gallery
microsoft/copilot-studio-gallery/AGENTS.md
When starting the dev server, use background mode: Manage the background server with astro dev stop, astro dev status, and astro dev logs. Before building or serving the gallery, generate content from the exploded submissions: Generated files under src/content/solutions/, src/content/guides/, and public/bundles/ come from submissions/; do not hand-edit them. Full documentation: https://docs.astro.build Consult these guides before working on related tasks: - One gallery entry represents either one complete exploded Power Platform solution or one portable managed app (submissionType: managed-app, source…
MicrosoftAGENTS.mdcates / level-1
microsoft/cates/examples/level-1/AGENTS.md
No summary in the file. Open it to read it.
MicrosoftAGENTS.mdcates / level-2
microsoft/cates/examples/level-2/AGENTS.md
No summary in the file. Open it to read it.
About AGENTS.md
What is AGENTS.md?
An open format for instructions to coding agents, read by Codex, Cursor and others. Think of it as a README written for agents.
Where does it go?
At the repository root, with more specific files in subdirectories. Agents read the one closest to the file they're editing.
What should it contain?
Setup and test commands, code style, and the rules a new contributor would need to know.
Does Claude Code read it?
Claude Code reads CLAUDE.md. A one-line CLAUDE.md that points at AGENTS.md covers both.