One search for your own team's files and the public ecosystem. See how real projects write their agent instructions, and bring the good ideas home.
MicrosoftCursor rulemicrosoft/rushstack/.cursor/rules/rush.mdc
You are a Rush monorepo development and management expert. Your role is to assist with Rush-related tasks while following these key principles and best practices: The standard directory structure for…
MicrosoftCopilot instructionsmicrosoft/rushstack/.github/copilot-instructions.md
You are a Rush monorepo development and management expert. Your role is to assist with Rush-related tasks while following these key principles and best practices: The standard directory structure for…
MicrosoftAGENTS.mdmicrosoft/rushstack/libraries/rush-daemon-protocol/AGENTS.md
This package is governed by an ultra-strict lint policy for generated code. All of the rules below are enabled to error in eslint.config.js via the shared local-node-rig/profiles/default/includes/eslint/flat/mixins/strict-codegen.js mixin. They apply…
MicrosoftAGENTS.mdmicrosoft/rushstack/libraries/rush-daemon-transport/AGENTS.md
This package is governed by an ultra-strict lint policy for generated code. All of the rules below are enabled to error in eslint.config.js via the shared local-node-rig/profiles/default/includes/eslint/flat/mixins/strict-codegen.js mixin. They apply…
MicrosoftAGENTS.mdmicrosoft/rushstack/libraries/rush-terminal-renderer/AGENTS.md
This package is governed by an ultra-strict lint policy for generated code. All of the rules below are enabled to error in eslint.config.js via the shared local-node-rig/profiles/default/includes/eslint/flat/mixins/strict-codegen.js mixin. They apply…
MicrosoftSkillmicrosoft/rushstack/skills/rushstack-best-practices/SKILL.md
Provides best practices and guidance for working with Rush monorepos. Use when the user is working in a Rush-based repository, asks about Rush commands (install, update, build, rebuild), needs help with project selection, dependency management, build caching, subspace configuration, or troubleshooting Rush-specific issues.
MicrosoftAGENTS.mdmicrosoft/agent-governance-toolkit/agent-governance-claude-code/AGENTS.md
The agent-governance-claude-code/ directory contains the first-party Claude Code plugin package for Agent Governance Toolkit. It wires AGT policy evaluation into Claude-native hooks, markdown commands, and a bundled MCP server.
MicrosoftAGENTS.mdmicrosoft/agent-governance-toolkit/agent-governance-dotnet/AGENTS.md
agent-governance-dotnet/ contains the .NET SDK for Agent Governance Toolkit: policy enforcement, execution rings, trust, SRE controls, MCP security, lifecycle management, and auditability for .NET applications.
MicrosoftAGENTS.mdmicrosoft/agent-governance-toolkit/agent-governance-opencode/AGENTS.md
Scope: this folder publishes @microsoft/agent-governance-opencode, the AGT governance plugin for OpenCode. OpenCode loads plugins in-process as async JS/TS functions. The plugin entry point is src/index.mjs, which: - caches a single loadPolicy() state per OpenCode process - maps AGT decisions (allow / review / deny) onto OpenCode's contract: - deny → throw new Error(...) from the hook - review → annotate output.args._agtreviewreason - allow → return undefined - exposes agtpolicystatus and agtpolicychecktext as both in-process custom tools and stdio MCP server…
MicrosoftAGENTS.mdmicrosoft/agent-governance-toolkit/agent-governance-python/agent-mesh/AGENTS.md
AgentMesh is a trust-first communication layer for AI agents — providing cryptographic identity, multi-dimensional trust scoring, scope chains, and governance enforcement for multi-agent systems. Architecture: 4-layer trust stack - All data models use Pydantic BaseModel - Identity: AgentIdentity with .sign(data: bytes) -> str (base64 Ed25519 signatures) - Trust scores: 5 dimensions — competence, integrity, availability, predictability, transparency - DID format: did:mesh:{hex} — see the proof-of-possession note under Boundaries: registry/app.py derives DIDs from the public key, while AgentDID.generate mints a random…
MicrosoftAGENTS.mdmicrosoft/agent-governance-toolkit/agent-governance-python/agent-mesh/sdks/AGENTS.md
This directory contains cross-language AgentMesh SDKs: These SDKs should stay conceptually aligned with the trust, identity, governance, and MCP security surfaces provided elsewhere in the repo. This directory reflects the repo layout at this point in time. Some language implementations may eventually move into standalone top-level directories such as agent-governance-golang/, agent-governance-rust/, or agent-governance-python/. If that happens, treat the standalone top-level directory as the primary home for new work. This directory should then be treated as legacy/shared-layout guidance for the code…
MicrosoftAGENTS.mdmicrosoft/agent-governance-toolkit/agent-governance-python/agent-os/AGENTS.md
Agent-OS is a governance-first kernel for AI agents — a Python framework providing policy enforcement, semantic intent classification, identity management, and execution control for autonomous AI agents. Architecture: 4-layer modular kernel Framework adapters route intervention points through HostSession and receive PolicyEvaluation. Raise the canonical PolicyViolationError.fromevaluationresult(result) for denied or escalated results. Hosts should surface str(error) and use error.evaluationresult.reasoncode for structured handling. Use conventional commits: feat:, fix:, docs:, test:, refactor:, chore:
MicrosoftAGENTS.mdmicrosoft/agent-governance-toolkit/agent-governance-python/AGENTS.md
agent-governance-python/ is the top-level home for first-party published Python packages in Agent Governance Toolkit. Use this directory for reusable SDK/package surfaces that are meant to be consumed directly by external Python users. Applications, dashboards, demos, and larger runtime/product assemblies should stay in the repo root, examples/, or other existing homes unless maintainers explicitly decide to promote them into this package workspace. - Prefer this directory for first-party Python packages that are published independently. - Keep package names, import paths, and…
MicrosoftAGENTS.mdmicrosoft/agent-governance-toolkit/agent-governance-python/agent-sre/AGENTS.md
Agent-SRE is an SRE toolkit for AI agent reliability — providing SLO management, error budgets, chaos engineering, progressive delivery, cost guardrails, incident management, and observability for autonomous AI agents. Key engines: Use conventional commits: feat:, fix:, docs:, test:, refactor:, chore:
MicrosoftAGENTS.mdmicrosoft/agent-governance-toolkit/agent-governance-rust/AGENTS.md
agent-governance-rust/ contains the Rust SDK workspace for Agent Governance Toolkit: policy enforcement, trust, audit, identity, lifecycle, execution rings, and MCP security surfaces for Rust applications.
MicrosoftAGENTS.mdmicrosoft/agent-governance-toolkit/AGENTS.md
Agent Governance Toolkit is a multi-package OSS monorepo for runtime governance of AI agents: policy enforcement, zero-trust identity, execution sandboxing, SRE, compliance, examples, docs, demos, SDKs, and publishing pipelines. Use this file for repository-wide routing. When you enter a subdirectory that has its own AGENTS.md, that narrower file takes precedence. This routing reflects the repo as it exists today while reserving room for approved language SDK migrations. Language SDKs may live in standalone top-level directories at the repository root. For…
MicrosoftAGENTS.mdmicrosoft/agent-governance-toolkit/docs/AGENTS.md
The docs/ tree powers the published documentation site for Agent Governance Toolkit: reference material, tutorials, architecture docs, threat modeling, compliance content, package pages, and integration guides. - Be precise and honest; do not claim a feature is shipped unless the repo actually contains it. - Prefer updating an existing page over creating a near-duplicate page. - Use repo-relative links that work from the current document location. - Match existing tone: technical, direct, and evidence-based. - Keep package names, CLI commands,…
MicrosoftAGENTS.mdmicrosoft/agent-governance-toolkit/examples/AGENTS.md
The examples/ directory is the preferred place for runnable, self-contained integrations and worked examples. For OSS contributors, examples are often the best starting point for proposing support for a new framework or ecosystem tool. Use examples/ when you want to: Prefer an example over a core package change when the external project is new, niche, or still proving community demand.
MicrosoftAGENTS.mdmicrosoft/agent-governance-toolkit/examples/demos/AGENTS.md
The demo/ directory contains live demonstrations of AGT capabilities, including real-service walkthroughs and visual dashboards. Demos should help users see the system working end-to-end without changing the core product contract.
MicrosoftCopilot instructionsmicrosoft/agent-governance-toolkit/.github/copilot-instructions.md
Multi-language monorepo for runtime governance of AI agents. Core is Python, with SDKs in TypeScript, Rust, .NET, and Go. Core Python packages live under packages/: Language SDKs: Other top-level directories: docs/ (MkDocs site), examples/ (runnable integrations), demo/ (live dashboards), pipelines/ (ESRP release automation), benchmarks/, fuzz/ (ClusterFuzzLite), notebooks/. Each subdirectory with an AGENTS.md has area-specific commands and boundaries: read it before changing code there. For major design changes, always ask a maintainer (a collaborator with the Maintain or Admin role) before…
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.
