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/copilotstudiosamples/copilot-instructionsgit clone --depth 1 https://github.com/microsoft/CopilotStudioSamplesWhat 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.01283 | $0.01283 |
| Opus 5 | $0.00642 | $0.00642 |
| Sonnet 5 | $0.00257 | $0.00257 |
| Haiku 4.5 | $0.00128 | $0.00128 |
Grade A, and why
CopilotStudioSamples 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 yesterday.
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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CopilotStudioSamples — Contributor Instructions
This repo uses Just the Docs (Jekyll theme) to generate a documentation site with sidebar navigation and full-text search.
Adding a New Sample
- Create a folder under the right category:
authoring/,extensibility/,ui/,contact-center/,sso/,testing/,guides/,infrastructure/ - Add a
README.md(exact casing) with YAML front matter:
---
title: My Sample # Appears in sidebar nav
parent: Embed # Must match parent page's title exactly
grand_parent: UI # Required for level 3 (grandchild) pages
nav_order: 8 # Numeric position among siblings
---
- Write the README with: description, prerequisites, setup instructions
- Update the parent category's
## Contentstable to include the new sample - Test locally:
bundle install && bundle exec jekyll serve
Hierarchy Levels
| Level | Front matter | Example |
|---|---|---|
| Category | title, nav_order, has_children: true, has_toc: false |
ui/README.md |
| Subcategory | title, parent, nav_order, has_children: true, has_toc: false |
ui/embed/README.md |
| Sample | title, parent, grand_parent, nav_order |
ui/embed/servicenow-widget/README.md |
| Deep page | nav_exclude: true, search_exclude: false |
Internal subfolders |
Power Platform Solutions (authoring/solutions/)
Solutions follow the PnP format:
authoring/solutions/my-solution/
├── README.md # Description, screenshots, install steps
├── assets/ # Screenshots and diagrams
├── solution/ # Packaged .zip file(s) ready to import
└── sourcecode/ # Unpacked source (pac solution unpack)
Front matter:
---
title: My Solution
parent: Solutions
grand_parent: Authoring
nav_order: 7
---
README should include: what it does, screenshots in assets/, import steps, connection references to configure, known issues. Update authoring/solutions/README.md Contents table after adding.
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.
- yesterday First seen · 176 lines · 1,283 tokens per session scan A 3ce811dfcaf3
CopilotStudioSamples copilot-instructions.md is an instructions file published in the GitHub repository microsoft/CopilotStudioSamples (791 stars, last pushed 1mo ago), licensed MIT. It adds 1,283 tokens to every session, about $0.0064 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.