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

agentcairn

v0.3.0

Published

The cairn command: link projects to a shared memory and wire Agent Cairn into Claude Code.

Readme

agentcairn

The command line for Agent Cairn: shared, persistent project memory for AI coding agents, stored in Neo4j.

Connect Claude Code (one command, every project)

You need a running Agent Cairn server and a token from its dashboard (Access → Create token). Then, once per machine:

claude mcp add cairn --scope user -e CAIRN_URL=http://localhost:8787 -e CAIRN_TOKEN=<token> -- npx -y agentcairn mcp

Check it with claude mcp list (it should say Connected), then restart Claude Code. If it says "MCP server cairn already exists in user config", run claude mcp remove cairn --scope user and add it again.

agentcairn mcp is a small bridge to your server. It takes the project from the folder Claude Code was started in (its .cairn.json, else the git remote), so there is nothing to configure per repository.

Commands

npx -y agentcairn <command>     # or: npm install -g agentcairn, then use `cairn`

cairn init [project-id]    # link this folder to a project; add hooks and a CLAUDE.md block
cairn doctor               # check the whole setup
cairn briefing             # print what an agent would be told
cairn resume               # everything needed to carry on where the last agent stopped
cairn remote <git-url>     # make another git URL resolve to this project
cairn install-command      # add the /cairn slash command to Claude Code
cairn mcp                  # the stdio bridge used above

cairn init writes .cairn.json, a .mcp.json server entry (only when the server is not already registered for every project; no secrets, the address and token come from your environment), Claude Code hooks and a short CLAUDE.md block. The hooks inject the briefing at session start (opening with where the last work stopped), record the session as it goes (what was asked, files, commits, uncommitted work; set CAIRN_SESSION_CAPTURE=meta or off to send less), remind the agent to write a handoff after substantial work, and stamp memories with the commit and author. Set CAIRN_URL and CAIRN_TOKEN in your environment for the hooks to reach the server.

Everything here runs on your machine, because the server cannot see your repository. See Using it with Claude Code. MIT licensed.