The osinfra-io platform GitHub Copilot CLI plugin marketplace. This is the group-level, installable counterpart to pt-ai-context: where pt-ai-context holds always-on custom instructions, this repo distributes on-demand skills, agents, and MCP integrations as versioned plugins.
Register the marketplace once, then install the plugins you want:
copilot plugin marketplace add osinfra-io/pt-ai-plugins
copilot plugin install platform-grouping@osinfra-io
copilot plugin install techne-agents@osinfra-ioBrowse everything available in the marketplace:
copilot plugin marketplace browse osinfra-io| Plugin | Description | Source |
|---|---|---|
| platform-grouping | Shared platform workflows as Copilot skills (e.g. create-pull-request, address-review-comments) |
this repo |
| techne-agents | The Nomos onboarding agent and its pt-techne-mcp-server tools |
federated from pt-techne-agents |
The techne-agents plugin runs the pt-techne-mcp-server as a Docker container. It requires:
- Docker — the MCP server runs via
docker run NOMOS_GITHUB_TOKEN— must be set in your environment; the MCP server uses it to read team specs, compute CIDRs, look up users, and open pull requests on your behalf
export NOMOS_GITHUB_TOKEN=<your-token>Without NOMOS_GITHUB_TOKEN, read tools return not_configured and write tools (PR creation) will not work.
Keep installed plugins current when new versions are released:
copilot plugin update techne-agents@osinfra-io
copilot plugin update platform-grouping@osinfra-io
# or update everything at once
copilot plugin update --allPlugins complement custom instructions — they do not replace them. The Copilot CLI plugin.json manifest has no field for custom instructions, so copilot-instructions.md and *.instructions.md remain distributed through pt-ai-context and COPILOT_CUSTOM_INSTRUCTIONS_DIRS. Use this marketplace for cross-cutting capabilities (skills, agents, MCP servers) that should be installable from any directory.
Each plugin is a directory under plugins/ containing a plugin.json manifest. The marketplace is defined in .github/plugin/marketplace.json.
Team-owned plugins may be federated — their plugin.json lives in the team's own repository and marketplace.json references it via source: osinfra-io/<repo>, avoiding duplication.
Releases follow the platform convention — push a vX.Y.Z tag and the release workflow publishes automatically.