Intelligent Terminal is an experimental fork of Windows Terminal that adds native support for AI agents through the Agent Client Protocol. It is for Windows users who want to manage compatible agent command-line tools alongside terminal tabs, profiles, themes, shells, and keyboard shortcuts, and the catalogue entries provide instructions, skills, hooks, and a plugin for working with it.
Borrowing it
Nothing to install: this file belongs to microsoft/intelligent-terminal. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/intelligent-terminal/main/.github/instructions/agents.instructions.mdgit clone --depth 1 https://github.com/microsoft/intelligent-terminalWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/microsoft/intelligent-terminal/agents)<a href="https://agentmods.dev/instructions/microsoft/intelligent-terminal/agents"><img src="https://agentmods.dev/badge/instructions/microsoft/intelligent-terminal/agents/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/microsoft/intelligent-terminal/agents"><img src="https://agentmods.dev/badge/instructions/microsoft/intelligent-terminal/agents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.08330 | $0.08330 |
| Opus 5.5 | $0.03332 | $0.03332 |
| Sonnet 5.5 | $0.01666 | $0.01666 |
| Haiku 4.5 | $0.00833 | $0.00833 |
Grade B, and why
intelligent-terminal agents.instructions.md scanned grade B with 1 finding 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 1mo 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
tools: ['*'] Copies of this mod
4 near-identical copies found in the catalogue:
- polish-academic-mcp agents.instructions.md — 100% identical, 4 lines differ
- copilot-instructions agents.instructions.md — 95% identical, 181 lines differ
- codebase agents.instructions.md — 95% identical, 235 lines differ
- custom_github_copilot_agent_builder agents.instructions.md — 95% identical, 20 lines differ
How it starts
The opening of the file, as written. The whole thing — 998 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Custom Agent File Guidelines
Instructions for creating effective and maintainable custom agent files that provide specialized expertise for specific development tasks in GitHub Copilot.
Project Context
- Target audience: Developers creating custom agents for GitHub Copilot
- File format: Markdown with YAML frontmatter
- File naming convention: lowercase with hyphens (e.g.,
test-specialist.agent.md) - Location:
.github/agents/directory (repository-level) oragents/directory (organization/enterprise-level) - Purpose: Define specialized agents with tailored expertise, tools, and instructions for specific tasks
- Official documentation: https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/create-custom-agents
Required Frontmatter
Every agent file must include YAML frontmatter with the following fields:
---
description: 'Brief description of the agent purpose and capabilities'
name: 'Agent Display Name'
tools: ['read', 'edit', 'search']
model: 'Claude Sonnet 4.5'
target: 'vscode'
---
Core Frontmatter Properties
description (REQUIRED)
- Single-quoted string, clearly stating the agent's purpose and domain expertise
- Should be concise (50-150 characters) and actionable
- Example:
'Focuses on test coverage, quality, and testing best practices'
name (OPTIONAL)
- Display name for the agent in the UI
- If omitted, defaults to filename (without
.mdor.agent.md) - Use title case and be descriptive
- Example:
'Testing Specialist'
tools (OPTIONAL)
- List of tool names or aliases the agent can use
- Supports comma-separated string or YAML array format
- If omitted, agent has access to all available tools
- See "Tool Configuration" section below for details
model (STRONGLY RECOMMENDED)
- Specifies which AI model the agent should use
- Supported in VS Code, JetBrains IDEs, Eclipse, and Xcode
- Example:
'Claude Sonnet 4.5','gpt-4','gpt-4o' - Choose based on agent complexity and required capabilities
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.
- 1mo ago First seen · 998 lines · 8,330 tokens per session scan B ca6f7c3b9232
intelligent-terminal agents.instructions.md is an instructions file published in the GitHub repository microsoft/intelligent-terminal (2,074 stars, last pushed today), licensed MIT. It adds 8,330 tokens to every session, about $0.0333 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
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
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, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.