How to consume the EOS plugin marketplace

Use APM to install EOS plugins with dependency resolution, security checks, and cross-runtime deployment. Install repository-independent skills globally by default so they remain available while working across repositories. Use a project installation when a repository or its CI pipeline depends on a plugin.

[!IMPORTANT] Do not use the native marketplace or plugin installer built into Claude Code, Cursor, Codex, or another runtime. Native installs do not create an APM lockfile, pin content hashes, resolve transitive dependencies, run APM’s pre-install security scan, or support apm audit --ci drift detection. Use APM for both global and project installations.

Register the marketplace

apm marketplace add tillotech/eos

APM registers the marketplace as eos. Confirm the registration and inspect the available plugins:

apm marketplace list
apm marketplace browse eos

Install repository-independent skills globally

Install reusable skills in the user scope so they are available across repositories:

apm install engineering@eos --global

Repeat the command for each package needed, retaining the --global flag. APM stores user-scope dependencies and their lockfile under ~/.apm/, scans the packages, and deploys supported primitives to the configured agent runtimes.

Some runtimes only support a subset of APM primitives at user scope. Review any compatibility warning from APM; a warning about an unsupported primitive does not mean that the package’s supported skills failed to install.

Install a repository dependency

Install without --global when a repository or its CI pipeline requires a specific EOS plugin:

apm install php-standards@eos

APM updates the project’s apm.yml and resolves the dependency graph into apm.lock.yaml. Commit both files so contributors and CI install the same commits and content hashes:

git add apm.yml apm.lock.yaml

Install in CI

Replay the committed lockfile without resolving newer package versions:

apm install --frozen
apm audit --ci

Treat a lockfile mismatch or audit failure as a failed build. Do not regenerate the lockfile in CI.

Update global plugins

Refresh the marketplace and update user-scope dependencies:

apm marketplace update eos
apm update --global
apm install --global

The update affects every repository that uses those global skills on the workstation.

Update project plugins

Refresh the marketplace cache, resolve newer matching plugin versions, and verify the result:

apm marketplace update eos
apm update
apm install
apm audit

Review and commit the resulting apm.yml and apm.lock.yaml changes.

See APM’s installing from marketplaces guide for the supported installation paths and the capabilities lost when using native runtime installers.