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/github/copilot-sdk/copilot-instructionsgit clone --depth 1 https://github.com/github/copilot-sdkWhat 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.01801 | $0.01801 |
| Opus 5 | $0.00901 | $0.00901 |
| Sonnet 5 | $0.00360 | $0.00360 |
| Haiku 4.5 | $0.00180 | $0.00180 |
Grade A, and why
copilot-sdk 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot SDK — Assistant Instructions
Quick purpose: Help contributors and AI coding agents quickly understand this mono-repo and be productive (build, test, add SDK features, add E2E tests). ✅
Big picture 🔧
- The repo implements language SDKs (Node/TS, Python, Go, .NET, Rust, Java) that speak to the Copilot CLI via JSON‑RPC (see
README.mdandnodejs/src/client.ts). - Typical flow: your App → SDK client → JSON-RPC → Copilot CLI (server mode). The CLI must be installed or you can connect to an external CLI server via the
CLI URL option (language-specific casing)(Node:cliUrl, Go:CLIUrl, .NET:CliUrl, Python:cli_url, Java:cliUrl).
Most important files to read first 📚
- Top-level:
README.md(architecture + quick start) - Language entry points:
nodejs/src/client.ts,python/README.md,go/README.md,dotnet/README.md - Java:
java/README.md,java/pom.xml,java/sdk/pom.xml,java/copilot-native/pom.xml - Test harness & E2E:
test/harness/*, Python harness wrapperpython/e2e/testharness/proxy.py - Schemas & type generation:
nodejs/scripts/generate-session-types.ts - Session snapshots used by E2E:
test/snapshots/(used by the replay proxy) - Docs style guide:
.github/instructions/docs-style.instructions.md(used fordocs/**)
Developer workflows (commands you’ll use often) ▶️
- Monorepo helpers: use
justtasks from repo root:- Install deps:
just install(runs npm ci, uv pip install -e, go mod download, dotnet restore) - Format all:
just format| Lint all:just lint| Test all:just test
- Install deps:
- Per-language:
- Node:
cd nodejs && npm ci→npm test(Vitest),npm run generate:session-typesto regenerate session-event types - Python:
cd python && uv pip install -e . --group dev→uv run pytest(E2E tests use the test harness) - Go:
cd go && go test ./... - .NET:
cd dotnet && dotnet test test/GitHub.Copilot.SDK.Test.csproj - .NET testing note: Never add
InternalsVisibleToto any project file when writing tests. Tests must only access public APIs. - Java:
cd java && mvn clean verify(full build + tests),mvn spotless:apply(format code before commit) - Java single test:
cd java && mvn test -Dtest=CopilotClientTest| single method:mvn test -Dtest=ToolsTest#testToolInvocation - Java format check only:
mvn spotless:check| Build without tests:mvn clean package -DskipTests - Java testing note: Always use
mvn verifywithout-qand without piping throughgrep. Never addInternalsVisibleToequivalent — tests must only access public APIs.
- Node:
- Use configured LSPs for supported operations like finding references instead of pattern matching, renaming symbols, etc.
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 · 74 lines · 1,801 tokens per session scan A cb5d8f000386
copilot-sdk copilot-instructions.md is an instructions file published in the GitHub repository github/copilot-sdk (10,441 stars, last pushed 2d ago), licensed MIT. It adds 1,801 tokens to every session, about $0.0090 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.