Skip to content
AgentsMesh CLI

Installing Community Packs

Community packs are shared collections of rules, commands, agents, or skills published to GitHub or other git hosts. Use agentsmesh install to bring them into your project.

Installing a pack

Terminal window
# Auto-discover everything from a repo
agentsmesh install github:community/ai-skills@v1.0.0


# Install specific skills from a subdirectory
agentsmesh install github:my-org/toolbox --path skills --as skills


# Install agents from a specific tag
agentsmesh install github:my-org/agents@v2.3.0 --as agents

After installation, packs are:

  • Stored in .agentsmesh/packs/{name}/
  • Tracked in .agentsmesh/installs.yaml
  • Merged into canonical config during agentsmesh generate

Reinstalling after a fresh clone

After cloning a repository that uses packs:

Terminal window
agentsmesh install --sync

This reads .agentsmesh/installs.yaml and reinstalls any packs missing from .agentsmesh/packs/.

Automate with postinstall

{
  "scripts": {
    "postinstall": "agentsmesh install --sync"
  }
}

Now npm install automatically restores packs.

What’s in installs.yaml

.agentsmesh/installs.yaml
version: 1
installs:
  - name: security-agents
    source: github:my-org/agents
    source_kind: github
    features:
      - agents
    path: agents
    as: agents
    original_ref: main
  - name: shared-skills
    source: github:my-org/skills@v1.0.0
    version: v1.0.0
    source_kind: github
    features:
      - skills
    original_ref: v1.0.0

Commit this file so teammates can reinstall the same packs. Rows are sorted by name; see the install reference for the full field list.

Gitignore recommendation

If packs are large, you can gitignore the pack contents and use --sync to restore them:

.gitignore
.agentsmesh/packs/

Previewing before installing

Terminal window
agentsmesh install github:org/repo --dry-run

Shows what would be installed without writing any files.

Non-interactive installation

For CI or scripts:

Terminal window
agentsmesh install github:org/repo --force

Skips all prompts and includes all resources.

Merge behavior

Pack contents merge with your local canonical config during generation. If a pack defines a rule named security and you also have .agentsmesh/rules/security.md, your local file takes precedence.

Priority order:

  1. Local .agentsmesh/ — always wins
  2. Packs (.agentsmesh/packs/)
  3. Extended sources (extends in agentsmesh.yaml)

Hooks are the exception: a pack’s hooks are never dropped. Two packs with hooks on the same event are combined, and a pack adds to an extends source’s hooks for that event instead of replacing them. When your hooks.yaml defines the same event, your hooks come first and the pack’s hooks follow. A pack hook with the same type, matcher and command (or prompt text) as one of yours is the same hook, and your copy wins. To drop a pack hook, uninstall the pack or leave hooks out of its features.