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

droid-factory

v0.0.4

Published

Install custom Factory Droid subagents and delegate work using custom slash commands.

Readme

Droid Factory install

Install custom Factory Droid subagents and delegate work using custom slash commands with a single npx droid-factory (or bunx droid-factory) call. By default it launches a guided, step‑by‑step installer where you pick the install location (personal or project) and choose which commands and droids to install; flags are available for non‑interactive “install everything” runs.

Usage

npx droid-factory
bunx droid-factory

The guided flow highlights existing files, lets you decide on overwrites, and ends with a concise summary.

Ensure Custom Droids are enabled in Factory (/settings → Experimental → Custom Droids) or by adding "enableCustomDroids": true to ~/.factory/settings.json; otherwise the installed commands cannot launch their helper agents.

Guided flow

  • Step 1/6 — Choose install location (Personal ~/.factory or Project ./.factory)
  • Step 2/6 — Choose source (Templates or Marketplace)

Templates (bundled):

  • Step 3/6 — Install all commands and droids?
  • Step 4/6 — Select commands to install
  • Step 5/6 — Select droids to install
  • Step 6/6 — Overwrite existing files if found?
  • Summary shows what was created/overwritten/skipped and next steps

Marketplace:

  • Step 3/6 — Enter marketplace (path/url/owner/repo)
  • Step 4/6 — Install all plugins?
  • Step 5/6 — Select plugins to install
  • Step 6/6 — Overwrite existing files if found?
  • Summary shows what was created/overwritten/skipped and next steps

Optional flags (non-interactive)

  • --yes — run without interactive confirmations
  • --dry-run — preview actions and summary without writing files
  • --scope personal|project and --path <repo-root> — target install location
  • --commands all|name1,name2 and --droids all|name1,name2 — select what to install
  • --only-commands, --only-droids — limit to one type
  • --force — overwrite existing files
  • --list — list available templates
  • --verbose — print the detailed plan
  • Marketplace: --marketplace <path|url|owner/repo>, --plugins all|name1,name2, --import marketplace|templates, --ref <branch-or-tag>, --debug

Contributing commands or droids

  1. Fork this repository.
  2. Add or modify Markdown templates in templates/commands/ or templates/droids/.
  3. Run npm test or npm run lint if scripts are provided (future roadmap).
  4. Verify your changes locally (see "Local development" below).
  5. Commit with clear messages and open a pull request against the main branch.
  6. Include before/after installer output as needed to demonstrate your change.

Local development

git clone https://github.com/iannuttall/droid-factory.git
cd droid-factory
npm install

node bin/droid-factory.js --dry-run --yes
node bin/droid-factory.js --yes

Use npm pack to sanity-check the tarball before publishing, and remember to bump package.json versions per semantic versioning guidelines.