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

@agentkrew/cli

v0.5.1

Published

AI engineering team for your coding agent: agents, skills, commands and workflows

Readme

@agentkrew/cli

AI engineering team for your coding agent: specialized agents, reusable skills, commands and multi-agent workflows — with the AI runtime treated as an adapter, not the source of truth.

AgentKrew is Claude Code-first. The same canonical agent/skill/command/workflow source renders to OpenCode and Codex without changes to the core.

Installation

No global installation required. Run directly with npx:

npx @agentkrew/cli --help

Commands

| Command | Description | | --------------------- | -------------------------------------------------- | | agentkrew init | Install AgentKrew into a project | | agentkrew doctor | Validate installation health | | agentkrew update | Update to latest version | | agentkrew list | List available agents, skills, commands, workflows | | agentkrew info | Show details for a specific artifact | | agentkrew validate | Validate kit quality | | agentkrew remove | Remove AgentKrew from project | | agentkrew demo | Replay a scripted /create-feature run | | agentkrew --help | Show help | | agentkrew --version | Show version |

Quick Start

By default, init fetches the kit from the AgentKrew license server, so it needs a license key (see Kit Sources for the local alternative):

# In your project root
export AGENTKREW_LICENSE_KEY="your-license-key"
npx @agentkrew/cli init --runtime claude --kit engineer

# Start Claude Code
claude

# Run a feature workflow
> /create-feature "Add user authentication"

Kit Sources

By default, kits are fetched from the AgentKrew license server. You need a valid license key:

export AGENTKREW_LICENSE_KEY="your-license-key"
npx @agentkrew/cli init --runtime claude --kit engineer

For local development, point --kit-path at the directory that contains your kit folders (the CLI appends the kit name to it):

npx @agentkrew/cli init --runtime claude --kit engineer \
  --kit-source local --kit-path ./packages/kits

Requirements

  • Node.js >= 22
  • A supported AI coding runtime (Claude Code, OpenCode, or Codex)

License

MIT © AgentKrew