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/intelligent-terminal/copilot-instructionsgit clone --depth 1 https://github.com/microsoft/intelligent-terminalWhat 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.01953 | $0.01953 |
| Opus 5 | $0.00977 | $0.00977 |
| Sonnet 5 | $0.00391 | $0.00391 |
| Haiku 4.5 | $0.00195 | $0.00195 |
Grade A, and why
intelligent-terminal 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 3d ago.
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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions for Windows Terminal
This is the source repository for Windows Terminal, Windows Console Host (conhost.exe), and shared components between them. It is a large C++ codebase built with MSBuild/Visual Studio targeting Windows.
Build
Requires Visual Studio (preferably Visual Studio 2026) with "Desktop Development with C++" and "Universal Windows Platform Development" workloads, plus the Windows 11 SDK (10.0.22621.0). The solution uses the .slnx format (OpenConsole.slnx), which requires MSBuild 17.10 or later. If you get "Invalid input 'OpenConsole.slnx'. The file type was not recognized.", update Visual Studio.
Build uses MSBuild via the CMD razzle environment. Run razzle.cmd once per terminal session to set up the environment, then use the build commands. Since razzle sets env vars in CMD, chain commands with && when calling from PowerShell (e.g., cmd /c ".\tools\razzle.cmd && bz"):
.\tools\razzle.cmd & rem One-time setup per session: finds MSBuild, sets PATH and env vars
bcz & rem Clean build the full solution (Debug by default)
bcz rel & rem Clean build in Release
bz & rem Incremental build (no clean) — much faster for iterating
bz rel & rem Incremental Release build
To build only the project in the current directory (instead of the full solution), cd into a project folder and use the exclusive variants:
cd src\cascadia\TerminalApp
bx & rem Incremental build of just this project
bcx & rem Clean + build of just this project
Three configurations exist: Debug, Release, and AuditMode (enables extra static analysis via CppCoreCheck).
Running
OpenConsole (console host): From a razzle environment, run opencon to launch OpenConsole.exe from the build output.
Windows Terminal: You cannot launch WindowsTerminal.exe directly — it is a packaged app. The easiest way is F5 in Visual Studio with CascadiaPackage as the startup project (set Debug > Application/Background process to "Native Only"). From the command line in a razzle environment:
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.
- 3d ago First seen · 134 lines · 1,953 tokens per session scan A e0cbd2b3718a
intelligent-terminal copilot-instructions.md is an instructions file published in the GitHub repository microsoft/intelligent-terminal (1,908 stars, last pushed today), licensed MIT. It adds 1,953 tokens to every session, about $0.0098 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
mini-swe-agent copilot-instructions.md
Copilot instructions for SWE-agent/mini-swe-agent, covering style guide, test style, bad and good.
copperhead CLAUDE.md
Instructions for copperheadhq/copperhead, covering claude.md, what this repo is, sources of truth, workflow (openspec) and architecture (per spec.md §2).
coddy-agent AGENTS.md
Instructions for coddy-project/coddy-agent, covering agent notes for coddy, repository navigation, builds, pre-commit gate and documentation contract.
agentscope-java code-review.instructions.md
Instructions for agentscope-ai/agentscope-java, covering java code standards, security check, performance check, documentation sync check and pr title check.
agentinsight-sdk-python AGENTS.md
Instructions for AgentInsight/agentinsight-sdk-python, covering agentinsight python sdk — 智能体执行规则, 1. 项目基本信息, 1.1 技术栈, 1.2 项目关键特征 and 1.3 项目目录结构.
codex-acp AGENTS.md
Instructions for cola-io/codex-acp, covering repository guidelines, project structure, build, test, run, coding style & conventions and testing guidelines.