  ▄▀█ ▀▄▀ █▀▄▀█
  █▀█ █ █ █ ▀ █
  Agent Extension Manager by AgentXM

  https://axm.sh | https://agentxm.ai

Extension manager for coding agents and AI assistants

Manage agent skills, subagents, commands, MCP servers and more. Use the right tool(s) for the job.
Bundle extensions with extension packs to share workflows across projects, teams, and others.
Switch effortlessly between coding agents, bringing your workflow with you. Avoid lock-in.

[!WARNING] axm is in early alpha testing. Capabilities and APIs may change. To be included in the test user group, reach out to hello@agentxm.ai.

Multi-tool — a unified context-engineering toolkit for managing skills, commands, subagents, and MCP servers
Multi-agent — share workflows across Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode, and nearly 40 others
Cross-platform — discover and distribute agent skills and extensions across package ecosystems including JavaScript, Python, Java, .NET, Go, Rust, Ruby, and more

Installation

Ask your agent to install axm:

Follow these install instructions to set up axm: https://axm.sh/install.md

macOS / Linux:

curl -fsSL https://axm.sh/install.sh | sh

Windows (PowerShell):

irm https://axm.sh/install.ps1 | iex

Windows (CMD):

curl -fsSL -o install.cmd https://axm.sh/install.cmd && install.cmd

Homebrew:

brew install agentxm/tap/axm

npx (no install, for agents and CI):

npx axm.sh --version

Getting started

Initialize axm in your project. axm detects your installed agents and creates an .axm/ workspace to manage extensions across all of them.

axm setup

See what's recommended for your project:

axm discover

Install an extension and axm wires it into every agent in your workspace:

axm install @acme/skills/code-review

Extension types

Type	What it is	Example
Skills	Context-triggered agent capabilities per the agentskills.io spec	`@acme/skills/code-review` — apply team review standards on every diff
Commands	User-invokable prompts (slash commands, saved prompts)	`@acme/commands/release-notes` — draft release notes from recent commits
Subagents	Task-specialized agents the main agent delegates to	`@acme/subagents/researcher` — delegate doc-reading to a cheaper model
MCP servers	Model Context Protocol servers exposing tools, data, and integrations	`@acme/mcp-servers/linear` — tools for reading and updating Linear issues
Extension packs	Curated bundles teams install and keep in sync	`@acme/packs/frontend-tools` — the frontend guild's standard skills and commands

Every type has its own subcommand namespace (axm skills, axm commands, axm subagents, axm mcp-servers, axm packs) sharing a common shape: install, uninstall, list, update, new, publish, plus enable/disable where it applies.

Subcommands

Examples below use skills; the same shape applies to every type.

axm skills new my-skill                       # Scaffold a new skill
axm skills fork my-skill                      # Fork an installed skill to customize
axm skills install @acme/skills/code-review
axm skills list
axm skills disable my-skill                   # Turn off without uninstalling
axm skills enable my-skill
axm skills publish my-skill                   # Publish to the registry

axm packs adds bundling commands:

axm packs add my-pack @acme/skills/code-review
axm packs add my-pack "effect-*"              # Add all matching extensions

Run axm --help for the top-level command list, or axm <command> --help for options on any subcommand.

Workspace

Top-level commands work across every extension type and infer the target from your input:

axm install                          # Sync extensions from .axm/settings.json
axm install @acme/skills/code-review # Install a single extension
axm update                           # Pull latest versions
axm outdated                         # Show extensions with available updates
axm uninstall @acme/skills/code-review
axm prune                            # Remove extensions axm isn't managing
axm upgrade                          # Update axm itself

Publishing

Extensions publish to the registry in four steps.

axm skills new my-skill              # 1. Scaffold
# 2. Author content in the scaffolded directory
axm lint                             # 3. Check the publish gate locally
axm skills publish my-skill          # 4. Publish

axm lint checks the same rules the registry enforces — see Lint for details.

Lint

axm lint evaluates workspace and per-extension invariants against a shared rule catalog — the same one that drives the registry publish gate.

axm lint                    # Report findings against the current project
axm lint --fix              # Apply every autofixable finding non-interactively
axm lint --scope user       # Lint the user-scope workspace
axm lint --strict           # Exit non-zero on warnings as well as errors
axm lint --json             # Machine-readable findings envelope

Project scope is the default. Local lint.rules overrides in .axm/settings.json affect axm lint only — the registry publish gate remains authoritative.

Authentication

axm login                   # Sign in to the default registry
axm whoami                  # Show the current identity
axm logout
axm token                   # Print the current token (for scripting)

Supported agents

axm supports nearly 40 agents — Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode, Windsurf, Cline, Continue, Roo, Goose, and more. If your agent isn't there, open an issue and we'll add it.

Development

This is an Nx monorepo.

pnpm install    # Install dependencies
pnpm build      # Build all packages
pnpm test       # Run tests
pnpm typecheck  # Type check
pnpm lint       # Lint

Use pnpm build:affected, pnpm test:affected, or pnpm lint:affected to only operate on packages changed since main.

See CONTRIBUTING.md for the full development workflow.

Open Agents, Open Standards, Open Source.

axm.sh

Quick Install