Copilot usage metrics now name your own skills, custom agents and MCP servers, listing up to 25 per record
An organization's own customizations are no longer lumped together, so admins can see which internal skills and MCP servers people actually use.
// Key points
- In enterprise and organization reports, including per-user 1-day and 28-day reports, skills, custom agents, MCP servers, slash commands and plugins show their configured names instead of being grouped together, and each record now lists up to 25 entries, up from five.
- Names come from Copilot CLI, the GitHub Copilot app, ACP integrations such as JetBrains, and the Copilot SDK; prompt mode, the app and ACP integrations need Copilot CLI 1.0.97 or later, and the SDK needs v1.0.21 or later, and IDE built-in chat telemetry doesn't report names.
- The data comes from client telemetry and can undercount; GitHub says to use it for trends and adoption, not exact accounting, and to review names before sharing reports outside the organization.
Builder's takePlenty of teams have built a pile of skills and MCP servers with no idea which get used. Now you can prune by usage: retire what nobody called in a month, and put tests and docs on the popular ones first. Names show up in reports, so keep customer names and internal codenames out of them.
// Background · from #Coding agents
Full timeline →- Oct 24 LiteLLM 1.107.0 was a poisoned release: malicious code ran through Python startup hooks and stole credentials without LiteLLM ever being imported
- Oct 24 Claude proves 239 entry points across 123 open-source libraries won't crash on any input up to 64 MB, at the RISC-V assembly level
- Oct 24 Enterprise installations for GitHub Apps are generally available, so enterprise governance and security automation no longer has to rely on classic PATs