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

mogkit

v0.1.1

Published

mogkit — the open-source toolkit for product managers. Scaffolds a PM workspace and installs Claude Code skills. Out-craft the room.

Readme

mogkit

The open-source toolkit for product managers. Scaffolds a Claude Code-ready PM workspace and installs the 13 mogkit skills.

npx mogkit init my-workspace
cd my-workspace
mogkit doctor

Then open the workspace in Claude Code and run any skill from .claude/skills/.

Commands

| Command | What it does | |---|---| | mogkit init [dir] | Scaffold a workspace; git init; install all 13 skills | | mogkit add | Interactive ingest of a file into sources/ with a type tag | | mogkit status | Corpus health report (count, type spread, gaps) | | mogkit skills list | List bundled skills + install state | | mogkit skills add <name> | Install a specific skill into .claude/skills/ | | mogkit doctor | Verify your setup; plain-language fixes for what's broken |

What's in a workspace

my-workspace/
├─ CLAUDE.md            # orients every Claude Code session in this workspace
├─ sources/             # raw research; versioned; grows over time
├─ graph/               # graph.json + graph.md (generated by `graphify`)
├─ knowledge/           # outputs of interrogation skills land here
└─ .claude/skills/      # all 13 skills installed

The 13 skills

Standalone (single-shot, paste-input): metrics-tree, spec-stress-test, narrative-review, tradeoff-frame, stakeholder-map, launch-readiness, interview-coach

Discovery engine (corpus-backed, stateful): graphify, discovery-query, assumption-audit, prd-interrogate, interview-guide, synthesis-map

Principles

  • Interrogator, not generator — no skill outputs a finished deliverable
  • Provenance or it doesn't exist — every claim traces to a source quote
  • Cold-start honesty — on a thin corpus, the skills say so loudly
  • One deep system, many sharp tools — Discovery is the only stateful engine
  • The CLI is thin — no LLM calls, no API key, zero SaaS deps

Full docs, the site, and the Workflow Library: https://github.com/Waddling-Penguin/mogkit

MIT licensed. Out-craft the room.