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

polygraph-claude-plugin

v0.4.15

Published

AI agent skills and subagents for Polygraph multi-repo coordination

Readme

What is Polygraph?

Polygraph is a standalone product for coordinating changes across multiple repositories. It lets AI agents delegate work to child agents in other repos, monitor CI across repos, and manage multi-repo sessions.

Skills

  • polygraph — Comprehensive guidance for multi-repo coordination: session init, delegation, branch pushing, PR creation, and session management
  • await-polygraph-ci — Wait for CI pipelines to settle across all repos in a session, investigate failures, and present fix options
  • get-latest-ci — One-shot fetch of the latest CI pipeline execution for the current branch

Agents

  • polygraph-init-subagent — Discovers candidate repositories and initializes a Polygraph session
  • polygraph-delegate-subagent — Delegates work to a child agent in another repository, polls for completion

Dist Layout

  • dist/claude — publishable Claude plugin npm package (polygraph-claude-plugin)
  • dist/codex — publishable Codex plugin npm package (polygraph-codex-plugin)
  • dist/opencode — generated OpenCode artifacts

Codex Installer

The publishable Codex package now exposes an explicit installer CLI:

npx polygraph-codex-plugin

That command copies the packaged Codex plugin into:

~/.agents/plugins/polygraph

installs the packaged custom Codex subagents into:

$CODEX_HOME/agents

updates the personal Codex marketplace at:

~/.agents/plugins/marketplace.json

so the polygraph plugin points at ./.agents/plugins/polygraph, and enables the plugin in:

$CODEX_HOME/config.toml

CODEX_HOME defaults to ~/.codex when unset.

To verify an install, run:

npx polygraph-codex-plugin check

Development

# Install dependencies
npm install

# Generate dist/ directly from source/
npm run sync-artifacts

Releasing

Run the Release PR GitHub Actions workflow with a version bump (patch, minor, or major). It opens a release PR against main instead of pushing directly. When that PR is merged, the Stage Release workflow automatically tags the release and stages both dist/claude and dist/codex on npm. A maintainer must then review and approve each staged package with 2FA before it is published to the live registry.

Configure each npm package's trusted publisher to allow npm stage publish from .github/workflows/publish.yml. For the strictest release flow, do not allow direct npm publish for the trusted publisher and disallow token-based publishing after the staged workflow has been verified.

Learn More

License

License information is defined in the package metadata.