Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

One manifest for every harness: APM, explained

Written November 9, 2026

APM promises one apm.yml manifest for every agent harness — skills, MCP servers, hooks, subagents. What it covers, what it doesn't, and the May date.

The problem: the same setup, maintained five times

A developer running several agent tools maintains the same skills, MCP servers, hooks, and subagents in every one of them — once for Copilot, once for Claude Code, once for Cursor, and so on. Each setup is hand-curated, undocumented, and drifts. Microsoft's Agent Package Manager (APM) is a dependency manager for that configuration: one apm.yml manifest in the project, and apm install deploys it to every tool.

What one manifest covers

An apm.yml declares instructions, skills, prompts, agents, hooks, plugins, and MCP servers, and APM writes them into the directories each tool already reads — .github/ for Copilot, .claude/ for Claude Code, .cursor/ for Cursor, and the equivalents for OpenCode, Codex, Gemini, Windsurf, Kiro, and Grok Build. Dependencies resolve from any git host, with versions pinned by tag and checked by content hash. A generated apm.lock.yaml pins the resolved tree the way package-lock.json does for npm, so a fresh clone reproduces the same setup.

Three mechanisms guard the supply chain: apm install scans package content for hidden Unicode that could hijack agent behaviour, the lockfile records content hashes for provenance, and apm audit rebuilds the expected configuration and diffs it against the working tree to catch hand-edits. An apm-policy.yml lets a team say which sources, scopes, and primitives are allowed, with tighten-only inheritance from enterprise to org to repo — a repo cannot relax a constraint set above it. The policy governs what gets installed; the agent tool governs what runs.

The date correction: May, not November

Stories in early November described APM as newly released. That is wrong. APM reached v0.12.2 on May 5, 2026, and the project dates to the previous autumn. What actually happened in November is narrower: Dependabot added version updates for dependencies declared in apm.yml, and the project drew fresh attention. Carry May as the date.

Verdict: use APM if your team runs two or more agent tools and wants identical instructions across them. Skip it if you are solo on one tool — the manifest and lockfile are overhead when one AGENTS.md already does the job.

What it does not do

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Dependabot now updates agent package managers · Agent Skills has a neutral home — and still no security story · Pick a memory server for your coding agent