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

@fleet-command-agents/cli

v1.0.8

Published

Public installer for Fleet Command: Agents — wire Claude Code, Codex, Cursor & Antigravity into the fleet layer above your coding agents: every session, every machine, one live space map on iPhone & Apple Watch. Each platform pairs as its own fleet. Thin

Readme

@fleet-command-agents/cli (public installer)

The public npm entry point for Fleet Command: Agents — the fleet layer above your coding agents: every Claude Code, Codex, Cursor & Antigravity session, on every machine, rolled into one live map on your iPhone & Apple Watch. Each platform pairs as its own fleet.

This package is a thin delegate. It contains no backend URL, no hook runtime, and no native dependencies. Its only job is to locate the real Fleet Commander runtime (which ships with the Claude Code marketplace plugin) and hand off to it.

Usage — version-pinned only

Always pin a version. Never run @latest (npx caches aggressively, and pinning is a supply-chain hygiene baseline):

# Codex / Cursor / Antigravity — each pairs as its own fleet
npx -y @fleet-command-agents/cli@<version> setup --agent codex       --code FLEET-XXXX
npx -y @fleet-command-agents/cli@<version> setup --agent cursor      --code FLEET-XXXX
npx -y @fleet-command-agents/cli@<version> setup --agent antigravity --code FLEET-XXXX

The pairing code (FLEET-XXXX) comes from the iPhone app's Add fleet screen. After wiring: Codex needs /hooks approval inside Codex; Cursor / Antigravity need an app restart to load the hooks. (Cursor & Antigravity are observe-only today.)

Claude Code

Claude Code installs via the Claude Code marketplace, not this CLI:

claude plugin marketplace add sideffect263/fleet-commander
claude plugin install fleet-commander

Then pair inside Claude Code: /fleet-link FLEET-XXXX.

How the delegate works

  1. If the marketplace plugin's stable runtime is already present at ~/.fleet-commander/scripts/fleet.mjs, this CLI spawns it directly.
  2. Otherwise it makes a best-effort, one-time fetch of the pinned runtime tarball from the published GitHub release of sideffect263/fleet-commander.
  3. If neither works, it fails honestly with the exact commands to install the Claude marketplace plugin first (which lays down the runtime), then re-run. It never half-wires an agent.

Relationship to the private plugin

The real onboarding logic — hook wiring, pairing, the backend URL, and the ask_human MCP server — lives in the private package @fleet-commander/plugin, which is marked private and is never published to npm. This public package deliberately holds none of those internals.

License

MIT