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

@izkac/forgekit

v0.3.37

Published

Forgekit CLIs — forgekit (install), forge (workflow), review (code review)

Readme

@izkac/forgekit

A disciplined development workflow for AI coding agents — portable across Claude Code, Cursor, Codex, Copilot, Gemini, Windsurf, and opencode.

npm node license

AI agents are fast but undisciplined: they claim success on stubs, skip verification, over-build, and quietly leave the human behind. Forgekit installs a gated workflow that holds an agent to the standards a senior engineer would — and gives you, the operator, the visibility and control to stay in charge of a whole fleet of them.

One package, three command-line tools:

| Bin | What it does | |-----|--------------| | forgekit | Install / update the Forge skills into any supported agent | | forge | Run the Forge workflow — sessions, integrity gates, fleet control | | review | Standalone multi-pass thorough code review |

Why Forge (the workflow)

Forge moves every substantial change through explicit phases — triage → brainstorm → plan → implement → verify → review → done — and enforces them with executable gates, not honor-system promises:

  • Operator brief — before any code is written, the agent produces a plain-language HTML explainer of what's about to be built (with diagrams). It opens in your browser and gates implementation: you approve what you actually understand, not a wall of spec markdown.
  • Runtime spine — every change declares how each capability wires up: library → runtime owner → what it writes → the evidence it works. No orphaned code that's "done" but never called.
  • Executable product loop — for jobs, workers, and pipelines the end-to-end acceptance is a command that must exit green, not a paragraph claiming it would.
  • Registered deferrals — "wire it up later" is only allowed when tracked; the finish gate refuses unresolved ones.
  • Session scorecard — every session leaves a graded, measurable trail (A–F).

The result: agents that can't fake completion, and a workflow you can trust to run with less babysitting.

Fleet control — command every session from one terminal

Running agents across three IDEs and two terminals? forge fleet is a single control surface over all of them, across every project and engine:

forge fleet list       # every session: phase, task progress, engine, activity
forge fleet watch      # live-refreshing dashboard (active sessions only; --all shows everything)
forge fleet view <s>   # detail + live transcript tail (Claude Code)
forge fleet send <s> "pause and report"   # message any session; --all broadcasts

Sessions auto-register the moment they touch Forge — including ones running inside Claude Desktop or Cursor. You see where everything stands at a glance and steer any of them without switching windows.

Portable — one workflow, every agent

The same skills and the same discipline, installed into each agent's native skills directory:

Claude Code · Cursor · Codex CLI · GitHub Copilot · Gemini CLI · Windsurf · opencode

Planning is engine-flexible too: use the OpenSpec CLI if you have it, or the built-in specs engine (plain markdown, same layout) if you don't. Optional ADRs archive each finished change into an Architecture Decision Record.

Install

npm i -g @izkac/forgekit
forgekit install            # interactive: pick skills + agents (space toggles, `a` = all)

Non-interactive:

forgekit install --skills forge,thorough-code-review --agents claude,cursor --force

Then wire a project and start working:

cd your-project
forge init --claude --cursor      # slash commands, rules, hooks, .forge/

# in the agent chat:
/forge add a health endpoint that returns { ok: true }

The agent triages, brainstorms with you, plans a tracked change, writes the operator brief for your approval, then implements task-by-task with TDD and per-task review — refusing to call itself done until the gates are green.

Docs

License

MIT. The Forge skill and several of its workflows are adapted from Superpowers (MIT).