GitHub Copilot: agents, skills, plugins, and hooks
·
Playbook
The right primitive for the task decides whether a workspace scales or collapses.
Most teams adopt GitHub Copilot as a single chat box, and it breaks at the second use case. This playbook treats routing as the first engineering decision: six primitives, agents, skills, plugins, MCP servers, hooks, and the configuration hierarchy, each with a boundary that decides whether the workspace scales. The payoff is measurable, roughly 30 percent less token spend per task, now billed in GitHub AI Credits, and output that stays consistent across the team.
6
Core primitives
6
Chapters
4
Routing questions
~30%
Token spend cut
Chapters
Reading tips
Keyboard shortcuts
Press / to search. Use j and k to move between chapters. Press t to toggle theme. Press g to go to top.