Agent Package Manager

This handles the full lifecycle of Agent Package Manager in your repository: initializing manifests, installing skills and MCP servers from GitHub or local paths, managing lockfiles for reproducible builds, compiling agent context into instruction files like AGENTS.md, and packing bundles for CI or air-gapped distribution. You'd reach for it when setting up apm.yml, auditing dependencies with dry runs, or troubleshooting stale cache issues after updates. The workflow is methodical and inspection-heavy, which makes sense given how easy it is to break agent configs with vague package references or self-referencing dependencies. If your team already has agent tooling in place, it respects that boundary instead of steamrolling your setup.

skills.sh installs: 479
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add webmaxru/enonic-agent-skills --skill agent-package-manager --agent claude-code

Installs into .claude/skills of the current project.

Files

Agent Package Manager

Procedures

Step 1: Assess the repository and the requested APM outcome

Inspect the repository root for apm.yml, apm.lock.yaml, .github/, .claude/, .cursor/, .opencode/, and apm_modules/.
Execute apm --version and apm config to confirm the installed CLI and current configuration.
If apm.yml exists, read references/manifest-and-lockfile.md before changing dependencies, scripts, or compilation settings.
If the request is about package installation, updates, pruning, or removal, read references/command-workflows.md before executing APM commands.
If no apm.yml exists and the user wants APM in the repository, initialize the project with apm init or apm init --yes.
If the repository already uses another agent configuration flow and the user did not ask to migrate it, limit the change to the requested APM scope instead of replacing the existing setup.