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

ai-team

v1.5.0

Published

AI agent team management CLI tool

Readme

ai-team

Drop a full AI product team into any project in one command — and keep them in sync as the templates evolve.

ai-team is a CLI that installs a curated set of AI agent definitions, skills, and workflows into your project and tracks them with a manifest so updates are always safe.

What you get

After running init your project gains:

  • Specialist agents — requirement analyst, planner, frontend dev, backend dev, code reviewer, tester, documentation writer, and orchestrator — ready to use in your IDE's agent runner
  • Shared skills — reusable prompt modules that agents load at runtime
  • Team workflows — pre-defined delivery and handoff sequences
  • Optional MCP config — wired-up tool servers for your IDE out of the box

Everything is tracked in .agents/manifest.json so the CLI knows exactly what it installed and can update safely without stomping on your customisations.

Installation

npm install -g ai-team
# or
pnpm add -g ai-team

Quick start

# Bootstrap your project (interactive)
cd my-project
ai-team init

# Or go fully non-interactive for CI / onboarding scripts
ai-team init --ide vscode --team web-product --include-mcp --yes

That's it. Open your IDE and your agent team is ready to go.

Verify the install

ai-team doctor

Example output:

✔ manifest found (.agents/manifest.json v0.1.0)
✔ 14 files installed, 0 missing
✔ 0 drifted files
✔ no migration candidates

Staying up to date

When the upstream templates ship improvements, pull them into your project without touching anything you've edited:

ai-team update

The sync engine compares hashes. Files you've modified locally are skipped and reported — never silently overwritten.

Preview before applying

Not sure what will change? Run a dry-run first:

ai-team plan

Example output:

~ .github/agents/backend-dev.agent.md   template changed, will update
  .github/agents/tester.agent.md        local drift detected, skipping (use --force to overwrite)
+ .agents/skills/visual-testing/SKILL.md  new file, will install

Force-overwrite a drifted file

ai-team update --force

Apply a legacy layout migration

If you're on an older install where agent files lived under .agents/teams/, move them to the current layout:

ai-team update --migrate

IDE support

| Flag | Installs agents to | MCP config | | ------------------- | --------------------------- | ------------------ | | --ide vscode | .github/agents/*.agent.md | .vscode/mcp.json | | --ide claude-code | .claude/agents/*.md | .mcp.json |

IDE is prompted interactively when not supplied.

Project layout after init

my-project/
├── .agents/
│   ├── manifest.json          ← install manifest (commit this)
│   ├── skills/                ← shared skill modules
│   ├── teams/web-product/     ← team workflows and README
│   └── custom/                ← your own extensions (never touched by CLI)
│       ├── skills/
│       ├── workflows/
│       └── agents/
├── .github/
│   └── agents/                ← agent entry files (vscode)
│       ├── frontend-dev.agent.md
│       ├── backend-dev.agent.md
│       └── ...
└── .vscode/
    └── mcp.json               ← MCP tool config (if --include-mcp)

Command reference

init

Install the agent team and write .agents/manifest.json.

ai-team init
ai-team init --ide vscode --team web-product --include-mcp --yes

| Flag | Description | | ------------------------------------ | ----------------------------- | | --ide <vscode\|claude-code> | Target IDE / agent runner | | --team <web-product> | Team profile to install | | --include-mcp / --no-include-mcp | Install MCP config | | --target <path> | Project root (default: cwd) | | --yes | Skip prompts, use flag values |

update

Sync installed files to the latest bundled templates.

ai-team update
ai-team update --force      # overwrite locally modified files
ai-team update --migrate    # apply safe legacy path moves

plan / diff

Dry-run: show what update would do without writing anything.

ai-team plan
ai-team diff   # alias

doctor

Validate manifest health, check for missing or drifted files, and preview any available migrations.

ai-team doctor
ai-team doctor --json   # machine-readable output for CI

version

Print the installed CLI version.

ai-team version
ai-team --version

Adding your own agents and skills

The CLI never reads or modifies anything under .agents/custom/. Use that directory freely:

.agents/custom/
├── skills/my-skill/SKILL.md
├── agents/my-agent.md
└── workflows/my-workflow.md

Reference your custom skills from any agent definition the same way built-in skills are referenced.

CI usage

# Check for drift in CI without modifying anything
ai-team doctor --json --target .

# Auto-apply safe updates in a release pipeline
ai-team update --yes --target .
  • .agents/custom/workflows/
  • .agents/custom/agents/

Update safety model

  • Copy-tracked files with local edits are skipped and reported
  • JSON assets (like MCP config) are merged structurally
  • Use --force to overwrite copy-tracked conflicts

Development

Run tests:

pnpm test

More documentation