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

lgmmo-forgekit-installer

v2.4.1

Published

One-command installer for LGM MMO ForgeKit into the current project.

Readme

ForgeKit

npm version CI GitHub repo

ForgeKit is a ForgeCode-native assistant kit for non-technical users.

Quickstart: 3 steps

  1. Open a terminal in your project and install ForgeKit:
    npx lgmmo-forgekit-installer
  2. Open ForgeCode in the same folder and ask for what you want:
    :ck:auto build me a todo app
  3. Read the Spec, approve it, then ForgeKit implements, verifies, and reports the result.

If you are not technical, start with plain language. You do not need to choose skills or tools.

Example Requests

Copy one and customize it:

:ck:auto build me a clean landing page for my coffee shop
:ck:auto fix the login bug where users cannot sign in
:ck:auto refactor this large dashboard module without changing behavior
:ck:auto add a Stripe checkout flow for monthly subscriptions
:ck:auto review this project and tell me what is broken

For more copyable templates, see examples/ck-auto-templates.md.

30-second Demo Flow

User: :ck:auto build me a todo app
ForgeKit: writes a short Spec in Vietnamese
User: đúng, làm đi
ForgeKit: routes to the right skill, edits files, runs verification
ForgeKit: reports changed files + how to test

Design Goals

  • ForgeCode native first.
  • One public entrypoint: :ck:auto.
  • Spec-first with one approval gate.
  • Token-efficient skill loading.
  • Non-technical user experience.
  • Optional adapters for Codex and Claude.
  • Optional RTK and Serena MCP integration.

Setup

Option A — One-command install with npm

npx lgmmo-forgekit-installer

Or install into a specific directory:

npx lgmmo-forgekit-installer --target ./my-project

After install, open ForgeCode in that directory and use:

:ck:auto <what you want built or fixed>

Option B — Use this repo directly

Clone or place this repo at ~/ForgeKit, then point ForgeCode to the kit root.

Option C — Generate .forge/ runtime export

python3 scripts/generate-forgecode.py --force

Codex / Claude Compatibility

  • Codex: npx lgmmo-codex-installer@latest or python3 scripts/generate-codex.py --force
  • Claude: python3 scripts/generate-claude.py --force

For Codex/Claude, use /ck:auto <what you want> (slash syntax).

Verification

npm test          # Run all tests
npm run lint      # Validate forgekit.json, registry, SKILL.md

Docs

Security

Do not commit runtime/private files: .credentials.json, .forge.db*, .env, .env.*.