This is an early release preview. You may encounter bugs.
APM logo
Unclaimed

Tool coding

APM

An open-source, community-driven dependency manager for AI agents.

Built by Microsoft

A 83/100 GitHub score ? This grade is derived from GitHub signals, not user votes. Open for the full breakdown.
Discussion

01 / Summary

About APM.

APM (Agent Package Manager) is a dependency manager for AI agent context, comparable to npm or pip but for the instructions, skills, prompts, agents, hooks, plugins, and MCP servers a coding agent uses. A project declares these in one manifest that ships with the repository, and a single install command configures every supported agent for anyone who clones it.

Packages come from GitHub, GitLab, Bitbucket, Azure DevOps, Gitea, or any git host, with version pinning and transitive dependency resolution. A lockfile records resolved sources and content hashes so a fresh clone reproduces the same content. Each target harness receives the primitives it supports, across GitHub Copilot, Claude Code, Grok Build, Cursor, OpenCode, Codex, Gemini, Windsurf, and Kiro. It can also author plugins with dependencies and export standard plugin packages, install from curated marketplaces, and bundle a configuration for distribution.

APM treats agent context as executable. Every install scans for hidden Unicode that could hijack agent behavior, pins integrity hashes, and blocks transitive MCP servers unless they are declared or trusted. An audit command repeats these checks on demand and detects hand-edited drift, and the lockfile exports a CycloneDX or SPDX software bill of materials.

A policy file lets an organization restrict allowed sources, scopes, and primitive types, enforced at install time with tighten-only inheritance from enterprise to organization to repository and an audit mode for CI gates. Policy covers what gets installed, while runtime behavior stays with the agent harness. APM builds on AGENTS.md, Agent Skills, and MCP, and pairs with agentrc for generating instructions from a codebase.

  • One manifest: instructions, skills, prompts, agents, hooks, plugins, and MCP servers declared in a single file
  • Multi-harness deployment: primitives installed into GitHub Copilot, Claude Code, Grok Build, Cursor, OpenCode, Codex, Gemini, Windsurf, and Kiro
  • Any git source: GitHub, GitLab, Bitbucket, Azure DevOps, Gitea, Gogs, or any git host, with version pinning
  • Transitive dependencies: packages depend on packages and the full tree is resolved
  • Lockfile integrity: resolved sources and content hashes pinned for reproducible installs
  • Content security: hidden-Unicode scanning and blocking of compromised packages at install time
  • MCP trust boundaries: transitive MCP servers need explicit consent
  • SBOM export: CycloneDX or SPDX inventory generated from the lockfile
  • Drift detection: audit rebuilds the agent context and diffs it against the working tree
  • Policy governance: org-wide allowlists with tighten-only inheritance and CI audit gates
  • Plugin authoring and marketplaces: build plugins with dependencies, export standard packages, and install from curated registries
  • CI integration: a GitHub Action for automated installs and audits

02 / Discussion CREDIBILITY-GATED

Discussion

Reading is open to everyone. Posting and voting need a verified identity or a GitHub grade of B or higher.

  • No discussions yet.

04 / Build

Build with APM.

Browse the catalog for frameworks, tools, and harnesses, each scored on real GitHub credibility.

Get APM →

Browse the catalog