Agent Package Manager (APM) solves the problem of sharing GitHub Copilot agents and skills across repositories without drift. Instead of manually copying files into .github/agents and .github/skills, APM provides a proper packaging model with versioning, dependency management, and runtime-aware installation. The post walks through a practical setup using scenario-based packages (architect, terraform, diagramming) that reference a single .github source of truth, and shows how APM can also configure MCP servers like Draw.io and Excalidraw as part of the install. The key insight is that agents and skills should be treated as platform engineering concerns with the same design thinking applied to other shared infrastructure.
Table of contents
Using .github as the source of truthScenario packages are a better fit than one shared bundleDiagramming is a good example of where packaging starts to matterOnce MCP is packaged as well, the model changesThe trade-offs are operational, not theoreticalWhy this matters more for platform teams than for individual reposSort: