apm vs ECC
Microsoft's dependency manager for agent context — declare skills, prompts, plugins and MCP servers in apm.yml; one install reproduces the setup across 8 clients with lockfile pinning and org policy. — versus — Cross-harness 'operating system' for coding agents — 268 skills, 66 agents, hooks, rules, memory persistence, instinct-based continuous learning and AgentShield security scanning. MIT.
Both ship reproducible agent-context setups across many clients. apm is a lean dependency manager (declare skills/prompts/MCP in apm.yml, lockfile-pinned installs); ECC ships the content itself — a batteries-included catalog of skills, agents, hooks and rules.
| apm | ECC | |
|---|---|---|
| Stars | 3.3k | 230k |
| Forks | 290 | 35k |
| Language | Python | JavaScript |
| License | MIT | MIT |
| Last activity | today | 2 days ago |
| Topics | coding, skills | coding, skills |
| Curated connections | 3 | 3 |
apm — the curator's take
The team/enterprise answer: apm.yml ships with the repo, so `git clone && apm install` gives every developer identical agent context — lockfile, transitive dependencies, drift detection, and an apm-policy.yml a security team can enforce with tighten-only inheritance. It's the only skill manager with a real governance story (SBOM export, MCP trust gates). NOT for quick personal use — manifest ceremony is overkill for 'just install this skill', where skillkit or asm is faster — and it targets 8 major clients, not the 40+ long tail. Young project; treat the roadmap as direction, not promise.
ECC — the curator's take
The kitchen-sink option, and the most popular one by a wide margin: one install gives Claude Code, Codex, Cursor, OpenCode and friends a full operating layer — session-memory hooks, learned instincts, quality gates, orch-* orchestrator commands, worktree lifecycle, security scanning — plus three genuinely good guides on token optimization, memory and agentic security. When NOT: it's maximalist. Hundreds of skills and global hooks add context weight, and the README's own top warning is about broken stacked installs — start with the minimal/no-hooks profile and never mix the plugin with the manual installer. If you only want one capability, take the surgical tool instead: claude-reflect for learning-from-corrections, pro-workflow for session memory, asm or skillkit for skill management. Watch the upsell surface (Pro app, sponsors) — the OSS core is MIT and complete.