npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

allagents

v1.19.0

Published

CLI tool for managing multi-repo AI agent workspaces with plugin synchronization

Readme

AllAgents

npm License: MIT Docs

Write AI agent skills once. Sync across every configured client. Manage across multiple repos.

AllAgents keeps your AI tooling (skills, agents, hooks, MCP servers) in one workspace and syncs it everywhere your team works — including Claude Code, GitHub Copilot, Cursor, Codex, OpenCode, and dozens more.

Quick Start

# Create a workspace from a shared template
npx allagents init my-workspace --from myorg/templates/nodejs
cd my-workspace

# Install a plugin, choosing its scope and target clients interactively
npx allagents plugin install code-review@claude-plugins-official

# Sync to all configured clients
npx allagents update

No cloning required — AllAgents fetches the workspace.yaml directly from GitHub and sets up everything.

Install the end-user AllAgents skill when you want your coding agent to operate the CLI using its current machine-readable command contracts:

npx allagents plugin install allagents@allagentsdev/allagents --scope user

How It Works

  1. Configure your workspace with repos, plugins, and target clients in workspace.yaml
  2. Sync — AllAgents copies skills, agents, hooks, and MCP servers to each client's expected paths
  3. Work — every team member gets identical AI tooling via git, across any client they choose
┌─────────────────┐
│   Marketplace   │  GitHub repos containing plugins
└────────┬────────┘
         │
         ▼
┌─────────────────┐
│    AllAgents     │  sync & transform
│      sync       │
└────────┬────────┘
         │
    ┌────┴────┬────────┬─────────┐
    ▼         ▼        ▼         ▼
.claude/  .github/  .cursor/  .agents/   client paths

Why AllAgents?

npx skills installs skills across a broad ecosystem of destinations, while npx plugins installs richer plugin artifacts into its supported clients. AllAgents manages skills, agents, hooks, commands, and MCP servers across curated AI coding clients from one declarative workspace.

| | npx skills | npx plugins | npx allagents | |---|---|---|---| | Config | Imperative | Imperative | Declarative (workspace.yaml) | | Scope | Single project | Single project | Multi-repo workspace | | Artifacts | Skills | Skills, agents, hooks, commands, MCP | Skills, agents, hooks, commands, MCP | | Clients | 79 destination IDs ([email protected]) | 2 (Claude, Cursor) | Curated coding-client registry plus compatibility aliases | | Team sharing | Each dev runs install | Each dev runs install | Git-versioned — clone and go | | Ongoing sync | One-shot install | One-shot install | allagents update keeps everything current | | Workspace awareness | None | None | WORKSPACE-RULES injected so AI knows all repos and skills | | Provider resilience | Per-client | Per-client | Switch clients instantly — same tooling everywhere |

workspace.yaml

workspace:
  source: ../shared-config
  files:
    - AGENTS.md

repositories:
  - path: ../my-project
    description: Main project
  - path: ../my-api
    description: API service

plugins:
  - code-review@claude-plugins-official
  - my-plugin@someuser/their-repo

clients:
  - claude
  - copilot
  - cursor

Commands

| Command | Description | |---|---| | allagents init <path> | Create a workspace (optionally --from owner/repo) | | allagents update | Sync all plugins to workspace | | allagents update --profile <name> | Reconcile an installed global profile | | allagents plugin install <spec> [--scope project\|user] [--client <clients>] [--yes] | Install a plugin for selected scope and clients | | allagents plugin uninstall <spec> | Remove a plugin | | allagents plugin list | List installed plugins and skills with source, scope, and clients | | allagents profile install <name> --yes | Install a declared global profile | | allagents profile list | List declared and installed profiles with clients and launchers | | allagents profile status [name] | Inspect declared and installed profiles | | allagents profile remove <name> --yes | Remove unchanged managed profile resources | | allagents skill add <name> [--from <source>] [--scope project\|user] [--client <clients>] [--yes] | Add source-backed skills for selected scope and clients (plural skills alias supported) | | allagents skill list | List skills and status | | allagents mcp add <name> <commandOrUrl> [--scope user \| --profile <name>] | Add, authenticate, and sync an MCP server | | allagents mcp reauth <name> [--scope user \| --profile <name>] | Reauthenticate an HTTP MCP server in one destination | | allagents mcp list [--scope user \| --profile <name>] | List MCP declarations in one destination | | allagents mcp tools <server> [--search <text>] [--scope user \| --profile <name>] | Discover a configured server's live tools | | allagents mcp call <server> <tool> [options] [--scope user \| --profile <name>] | Inspect or call a live MCP tool | | allagents workspace status | Show workspace state | | allagents self update | Update AllAgents CLI |

See the full CLI reference for all options.

Supported Clients

AllAgents has one canonical, capability-aware client registry. It covers shared .agents/skills/ destinations, provider-specific skill roots, and project-only clients, while separately recording instruction, command, agent, hook, GitHub overlay, MCP, native, and profile support. Compatibility aliases such as claude-code and github-copilot normalize to their canonical AllAgents IDs.

See the client support matrix for paths, hooks, commands, and MCP support per client.

Plugin Structure

my-plugin/
├── skills/          # Reusable prompts (all clients)
│   └── debugging/
│       └── SKILL.md
├── agents/          # Agent definitions
├── commands/        # Slash commands (Claude, OpenCode)
├── hooks/           # Lifecycle hooks (Claude, Factory, Copilot, Codex)
├── .codex-plugin/   # Codex plugin manifest and explicit hook paths
├── .github/         # Copilot/VSCode project overrides
└── .mcp.json        # MCP server configs

For Codex project sync, AllAgents copies skills into .codex/skills/, merges plugin hooks into .codex/hooks.json, and preserves user-owned hooks already in that file. Codex plugins can declare hooks in .codex-plugin/plugin.json with a hooks path, path array, inline object, or inline object array; otherwise AllAgents falls back to hooks/hooks.json.

For Copilot project sync, AllAgents combines plugin hook declarations from hooks.json or hooks/hooks.json in .github/hooks/allagents.json and binds COPILOT_PLUGIN_ROOT for each plugin. Other repository hooks under .github/hooks/ remain project-scoped and are never promoted into the user-global ~/.copilot/hooks/ directory. Copilot package metadata under .github/plugin/ is not copied into the project overlay. Potential user-scope copies from older versions are left untouched and reported for manual review because their ownership was not tracked.

Marketplace registration and plugin.json are not required for direct plugin sources. A plugin without a supported hook declaration continues syncing its other artifacts. AllAgents warns and omits a declaration that cannot be read or parsed as JSON or lacks the version-1 hooks object envelope. A declaration with disableAllHooks: true adds no entries; otherwise, a non-array event value also omits the declaration. Skipping a declaration does not reject the plugin or itself suppress other eligible artifacts, including repository hook files.

Documentation

Full documentation at allagents.dev:

Related Projects

License

MIT