GitHub Copilot Terminology Glossary | GitHub Copilot Learning Hub
Skip to main content Terminology Terminology Definitions for the terms you’ll meet while exploring agents, skills, instructions, and related GitHub Copilot concepts. Core Concepts Use this page as a quick reference when reading articles in the Learning Hub or browsing the repository. Agent — A specialized configuration file ( *.agent.md ) that defines a GitHub Copilot persona or assistant with specific expertise, tools, and behavior patterns.
In products that support delegation, the agent is usually the primary coordinator or main session persona, while subagents handle narrower delegated tasks. When to use : For recurring workflows that benefit from deep tooling integrations and persistent conversational context. Learn more : What are Agents, Skills, and Instructions Subagent — A temporary, task-focused agent launched by another agent or orchestrator. A subagent usually gets a narrower prompt, its own isolated context window, and returns a summary back to the main agent instead of staying in the primary conversation.
When to use : For isolated research, parallel analysis, specialized review passes, or delegated implementation steps. Learn more : Agents and Subagents Built-in Tool — A native capability provided by GitHub Copilot without requiring additional configuration or MCP servers. Examples include code search, file editing, terminal command execution, and web search. Built-in tools are always available and don’t require installation.
Related terms : Tools , MCP Chat Mode — Deprecated terminology - This term is no longer used. Use Agent instead. Previously, “chat mode” was an alternative term for Agent that described how GitHub Copilot Chat could be transformed into domain-specific assistants. The ecosystem has standardized on “Agent” as the preferred terminology. See : Agent Collection — Note : Collections are a concept specific to the Awesome GitHub Copilot repository and are not part of standard GitHub Copilot terminology.
A curated grouping of related skills, instructions, and agents organized around a specific theme or workflow. Collections are defined in YAML files ( *.collection.yml ) in the collections/ directory and help users discover related customizations together. Example : The “Awesome Copilot” collection bundles meta-skills for discovering and generating GitHub Copilot customizations. Learn more : What are Agents, Skills, and Instructions Custom Agent — See Agent .
The term “custom” emphasizes that these are user-defined configurations rather than GitHub Copilot’s default behavior. Custom agents can be created by anyone and shared via repositories like Awesome GitHub Copilot. Custom Instruction — See Instruction . The term “custom” emphasizes that these are user-defined rules rather than GitHub Copilot’s built-in understanding. Custom instructions are particularly useful for codifying team-specific standards and architectural decisions.
Configuration & Metadata Front Matter — YAML metadata placed at the beginning of Markdown files (between --- delimiters) that provides structured information about the file and controls its behavior. In this repository, front matter typically includes fields like name , description , mode , model , tools , and applyTo . The front matter is what controls: Tool access : Which built-in and MCP tools the customization can use Model selection : Which AI model powers the customization Scope : Where the customization applies (e.g., applyTo patterns for instructions) Note : Not all fields are common across all customization types.
Refer to the specific documentation for agents, skills, or instructions to see which fields apply to each type. Example : --- name : 'React Component Generator' description : 'Generate modern React components with TypeScript' mode : 'agent' tools : [ 'codebase' ] --- Used in : Skills, agents, instructions, and Learning Hub articles. Handoff — A VS Code custom-agent frontmatter property ( handoffs ) that defines suggested transitions from one agent to another, often with a pre-filled follow-up prompt.
Handoffs are useful for guided workflows such as research -> implementation or planning -> review. Important : GitHub’s custom agent configuration reference says handoffs are currently ignored for Copilot cloud agent on GitHub.com, so this concept is not portable across every Copilot surface. Learn more : Agents and Subagents , Building Custom Agents AGENTS.md — An emerging industry standard file format for defining portable AI coding instructions that work across different AI coding tools (GitHub Copilot, Claude, Codex, and others).
The AGENTS.md file, typically placed in a repository root or .github/ directory, contains instructions for how AI assistants should interact with your codebase. Unlike tool-specific customization files ( .agent.md , .prompt.md , .instructions.md ), AGENTS.md aims to provide a standardized, platform-agnostic way to define AI behavior that can be consumed by multiple tools. Key characteristics : Platform-agnostic format for cross-tool compatibility Typically contains project context, coding standards, and architectural guidelines Located at repository root or in .github/ directory Learn more : AGENTS.md Specification Related terms : Instruction , Front Matter Instruction — A configuration file ( *.instructions.md ) that provides persistent background context and coding standards that GitHub Copilot reads whenever working on matching files.
Instructions contain style guides, framework-specific hints, and repository rules that help Copilot align with your engineering practices automatically. When to use : For long-lived guidance that applies across many sessions, like coding standards or compliance requirements. Learn more : What are Agents, Skills, and Instructions , Defining Custom Instructions Skills & Interactions Persona — The identity, tone, and behavioral characteristics defined for an Agent .
A well-crafted persona helps GitHub Copilot respond consistently and appropriately for specific domains or expertise areas. Example : A “Database Performance Expert” persona might prioritize query optimization and explain concepts using database-specific terminology. Related terms : Agent Prompt — Deprecated — Prompts ( *.prompt.md ) were reusable chat templates that captured specific tasks or workflows, invoked using the / command in GitHub Copilot Chat.
Prompts have been superseded by Skills , which offer the same slash-command invocation plus agent discovery, bundled assets, and cross-platform portability. If you have existing prompts, consider migrating them to skills. See Creating Effective Skills for guidance. See : Skill Skill — A self-contained folder containing a SKILL.md file and optional bundled assets (reference documents, templates, scripts) that packages a reusable capability for GitHub Copilot.
Skills follow the open Agent Skills specification and can be invoked by users via /command or discovered and invoked by agents automatically. Key advantages : Agent discovery : Extended frontmatter lets agents find and invoke skills automatically Bundled assets : Reference files, templates, and scripts provide richer context Cross-platform : Portable across coding agent systems via the Agent Skills specification Example : A /generate-tests skill might include a SKILL.md with testing instructions, a references/test-patterns.md with common patterns, and a templates/test-template.ts starter file.
When to use : For standardizing how Copilot responds to recurring tasks, especially when bundled resources improve quality. Learn more : What are Agents, Skills, and Instructions , Creating Effective Skills Platform & Integration MCP (Model Context Protocol) — A standardized protocol for connecting AI assistants like GitHub Copilot to external data sources, tools, and services. MCP servers act as bridges, allowing Copilot to interact with APIs, databases, file systems, and other resources beyond its b
The rest of this page is on the live site.