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

@oomerevren/tryforge

v0.1.3

Published

The Homebrew for AI Agents — one CLI for skills, MCPs, plugins, agents

Readme

Forge — The Universal Package Manager for AI Agent Context, Skills & MCPs

Stop manually copying .cursorrules and mcp.json across 5 different AI editors. One command to rule them all.

CI npm version npm downloads license MIT registry GitHub stars

npx -y tryforge doctor
forge add agent-security-auditor

3-second wow: forge add agent-security-auditor writes rules to Cursor, Claude, Codex, Windsurf — simultaneously.


Why Forge?

You're using Claude Code + Codex + OpenCode + Cursor. You want the same security rules, MCP servers, and skills everywhere. Today you:

  1. git clone a repo
  2. Copy SKILL.md to 4 different folders
  3. Manually paste the same rules into .cursorrules, CLAUDE.md, .windsurfrules
  4. Repeat for every new skill, every update

Forge fixes it. One command → every editor. Deterministic forge.toml → your whole team ships the same AI context.

| | Manual Setup | Forge | |---|---|---| | Multi-editor support | ❌ Copy-paste × 4 | ✅ One command | | Version pinning | ❌ None | ✅ forge.lock + SHA-256 | | Security audit | ❌ Zero | ✅ AST scanner (HIGH = refuse) | | Team sync | ❌ Out of sync | ✅ forge sync | | Updates | ❌ Manual | ✅ forge update | | Zero-install | ❌ | ✅ npx -y tryforge |


Install

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/oomerevren-beep/forge/main/install.sh | sh

# Windows PowerShell
irm https://raw.githubusercontent.com/oomerevren-beep/forge/main/install.ps1 | iex

# Or with Node 22+
npm i -g tryforge
npx -y tryforge doctor   # zero-install — no global install needed

Quick Start (60 seconds)

# 1. Initialize your project
npx forge init

# 2. Add the packages you want
forge add github:my-org/agent-security
forge add pdf/merge
forge add mcp/filesystem

# 3. Sync every editor
npx forge sync

Done. Cursor, Claude Code, Codex, OpenCode, Windsurf, DSH — all share the same context.


Supported Harnesses

| Harness | Status | Rule Format | |---------|:------:|-------------| | Claude Code | ✅ | CLAUDE.md merged blocks | | Cursor | ✅ | .cursor/rules/*.mdc | | OpenCode | ✅ | AGENTS.md shared blocks | | Codex | ✅ | AGENTS.md shared blocks | | Windsurf | ✅ | .windsurfrules merged | | DSH | ⚠️ | AGENTS.md (community) | | Generic | ✅ | .forge/ fallback |


Team Sync — forge.toml

# forge.toml — single source of truth for your project's AI context
[project]
name = "my-app"
version = "1.0.0"

[dependencies]
"agent-pr-reviewer" = "^1.2.0"
"mcp-filesystem" = "^1.0.0"

[skills.team-rules]
source = "github:my-org/team-skills"
ref = "main"

[agents.developer]
model = "claude-3-7-sonnet"
system_prompt = "Senior engineer. TDD. No shortcuts."

[mcp.servers.postgres]
command = "npx"
args = ["-y", "@modelcontextprotocol/server-postgres", "postgresql://localhost/db"]

[permissions]
denied_paths = [".env*", "id_rsa*", "./secrets"]
allow_network = false
# Everyone on the team runs:
git pull
npx forge sync
# That's it — identical AI context across every editor

Security

Forge is fail-closed by default:

  • sha256 verification — every package is hash-pinned; mismatch = exit 1
  • Static scanner — 19 rules (shell-danger, prompt-inject, perm-violation); HIGH blocks install
  • forge audit — flags mock/unverified installs (exit 1 on high-severity)
  • forge.toml [permissions] — denied paths enforced per-project
forge audit                    # scan installed packages
forge test ./my-package        # pre-publish validation
forge verify ./my-package      # full schema + security + adapter check

Available Packages

21 verified packages (sha256-pinned). Registry is git-native and forkable.

| Category | Examples | |----------|----------| | Skills | cmd/plan, cmd/review, obra/superpowers | | MCP Servers | mcp/filesystem, mcp/github, mcp/postgres, mcp/memory, mcp/sequential-thinking | | Agents | agency/frontend, agency/backend | | PDF Tools | pdf/merge, pdf/split, pdf/forms, pdf/ocr, pdf/extract, pdf/compress, pdf/convert, pdf/tables |

forge search pdf
forge search mcp
forge info mcp/github

Commands

| Command | What it does | |---------|-------------| | forge add <pkg> | Install to all harnesses (registry, GitHub, local) | | forge remove <pkg> | Uninstall from all harnesses | | forge install | Install all [dependencies] from forge.toml | | forge install --frozen | CI mode: exact from forge.lock | | forge sync | One-command team sync (skills + rules + MCP + roles) | | forge init <name> | Scaffold a new package | | forge test <pkg> | Validate against adapter matrix (dry-run) | | forge pack | Build verified tarball | | forge verify <pkg> | Schema + security + adapter check | | forge audit | Scan installed packages (fail-closed) | | forge doctor | Health check harnesses + store | | forge search <query> | Fuzzy search (<200ms, offline) | | forge list | List installed packages | | forge outdated | Show packages with newer versions | | forge update | Update all (or one) to latest | | forge tui | Interactive terminal dashboard |


Architecture

CLI (TypeScript)
  ├─ registry client (index.json + semver)
  ├─ store (~/.forge/ + links.json + cache)
  ├─ adapters (1 file per harness — symlink or copy)
  ├─ core (merge engine, security scanner, lock, sources)
  └─ commands (add/remove/sync/audit/test/pack/verify/tui)

v0.1 → v0.2 → v1.0:

  • v0.1 (now): 7 harnesses, 21 verified packages, full CLI
  • v0.2: forge publish, Rust rewrite for cargo install
  • v1.0: Team registry, brew install forge, winget

See docs/ROADMAP.md.


Add a Package

# 1. Create your package
forge init my-skill --type skill --yes
# Edit SKILL.md + forge.toml

# 2. Verify it
forge verify .

# 3. Publish (v0.2: tarball + GitHub Release + registry PR)

Until publish lands, open a PR adding registry/packages/<slug>.json + run npm run registry:build -- --check.


Add a Harness

One file: cli/src/adapters/<name>.ts. Implement the Adapter interface. Register in adapters/index.ts. Done.

See docs/ADAPTERS.md.


Documentation


Badges

Add forge to your project:

[![Managed by Forge](https://img.shields.io/badge/Agent%20Context-Forge-6366f1?style=flat-square&logo=anthropic)](https://github.com/oomerevren-beep/forge)

FAQ

Is this just for Claude Code? No. 7 harnesses today, one file per new harness. The point is universal.

Does install.sh need forge.sh domain? No. Works from GitHub raw today.

Are packages verified? 21 are sha256-pinned and pass the static scanner. The rest is tracked for Phase 13.

Windows support? Full. Junction on dirs, file-by-file copy fallback for non-ASCII paths, PowerShell installer.

Private registry? Yes. Fork this repo, keep registry/ private, point ~/.forge/config.toml to your own index.


License

MIT — see LICENSE.


Star this repo to get notified at v1.0. forge add → 7 places at once. forge sync → team sync. Homebrew simple.