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/p.808/copilot-instructionsgit clone --depth 1 https://github.com/microsoft/P.808What 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.00781 | $0.00781 |
| Opus 5 | $0.00391 | $0.00391 |
| Sonnet 5 | $0.00156 | $0.00156 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
P.808 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions
Code Style and Formatting
Function Documentation
Python
Every function must include a docstring inside the function body, immediately after the
def line. Use the following format:
def calculate_mos(ratings, num_subjects):
"""
Calculate the Mean Opinion Score from a list of ratings.
:param ratings: List of numeric ratings.
:param num_subjects: Number of subjects who provided ratings.
:return: The computed MOS value as a float.
"""
...
JavaScript
Every function must have a JSDoc comment above the function declaration:
/**
* Calculate the Mean Opinion Score from a list of ratings.
*
* @param {number[]} ratings - List of numeric ratings.
* @param {number} numSubjects - Number of subjects who provided ratings.
* @returns {number} The computed MOS value.
*/
function calculateMos(ratings, numSubjects) {
...
}
Python Spacing and Syntax
Follow PEP 8 conventions:
- Use 4 spaces per indentation level. Do not use tabs.
- Surround top-level function and class definitions with two blank lines.
- Surround method definitions inside a class with one blank line.
- Use spaces around operators (
=,+=,==,!=,<,>,in,not in, etc.). - No spaces immediately inside parentheses, brackets, or braces:
- ✅
func(a, b)— ❌func( a, b ) - ✅
data[0]— ❌data[ 0 ] - ✅
{'key': value}— ❌{ 'key' : value }
- ✅
- Place one space after commas in argument lists, collections, and imports.
- No trailing whitespace on any line.
- Keep lines to a maximum of 120 characters.
- Use snake_case for functions and variables, PascalCase for classes, and UPPER_SNAKE_CASE for constants.
- Imports should be grouped in the following order, separated by a blank line:
- Standard library imports
- Third-party imports
- Local / project imports
Line Endings
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 · 93 lines · 781 tokens per session scan A efcd16ca27c8
P.808 copilot-instructions.md is an instructions file published in the GitHub repository microsoft/P.808 (230 stars, last pushed 14d ago), licensed MIT. It adds 781 tokens to every session, about $0.0039 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.