intelligent-terminal agents.instructions.md

A set of guidelines for creating custom agent files that give GitHub Copilot specialized expertise, instructions, tools, and model settings for particular development tasks.

In plain words
What is it for?
Use it when creating or reviewing Markdown agent files for repository, organization, enterprise, or VS Code workflows.
Why use it?
It helps ensure agent files have the required metadata and are organized so Copilot can use the right specialist in the right place.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/microsoft/intelligent-terminal/agents
Clone the repo
git clone --depth 1 https://github.com/microsoft/intelligent-terminal

Made for: GitHub Copilot.

Per session 8,330 This file is loaded in full into every session.
When invoked 8,330 The same file — it is already loaded in full.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.08330 $0.08330
Opus 5 $0.04165 $0.04165
Sonnet 5 $0.01666 $0.01666
Haiku 4.5 $0.00833 $0.00833

Measured 2d ago against content hash ca6f7c3b9232, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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: ['*']
Origin

Copies of this mod

3 near-identical copies found in the catalogue:

.github/instructions/agents.instructions.md · 998 lines

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) or agents/ 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 .md or .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

Read the full file on GitHub · 998 lines

Changes

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.

  1. 2d ago First seen · 998 lines · 8,330 tokens per session scan B ca6f7c3b9232

Subscribe to this mod's changes

intelligent-terminal agents.instructions.md is an instructions file published in the GitHub repository microsoft/intelligent-terminal (1,908 stars, last pushed today), licensed MIT. It adds 8,330 tokens to every session, about $0.0417 per session on Opus 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.