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

agentsify

v0.1.0

Published

Bootstrap agent-agnostic AI configuration for any repository

Readme

agentsify

Bootstrap agent-agnostic AI configuration for any repository.

The problem

Every AI coding agent reads instructions from its own location:

| Agent | Instructions file | Rules directory | |---|---|---| | Claude Code | CLAUDE.md | .claude/rules/ | | Cursor | .cursorrules | .cursor/rules/ |

Maintaining the same content across multiple files is tedious and error-prone.

The solution

Keep a single source of truth — AGENTS.md and .agents/ — and let each agent read from it via symlinks.

Target repository structure

your-repo/
├── .agents/              # source of truth (committed to git)
│   ├── rules/
│   │   ├── coding.md
│   │   └── testing.md
│   └── skills/
│       └── deploy.md
├── AGENTS.md             # project instructions (committed to git)
│
├── CLAUDE.md             → AGENTS.md (symlink, gitignored)
├── .cursorrules          (gitignored)
├── .claude/
│   ├── rules/            → ../.agents/rules (symlink, gitignored)
│   └── skills/           → ../.agents/skills (symlink, gitignored)
├── .cursor/
│   ├── rules/            → ../.agents/rules (symlink, gitignored)
│   └── skills/           (gitignored)
└── .gitignore            # auto-updated by agentsify

Committed to git: AGENTS.md, .agents/

Gitignored (generated by agentsify): CLAUDE.md, .cursorrules, .claude/rules, .claude/skills, .cursor/rules, .cursor/skills

Usage

npx agentsify             # setup all agents
npx agentsify --claude    # setup only Claude Code
npx agentsify --cursor    # setup only Cursor
npx agentsify check       # verify symlinks are correct

Run agentsify once after cloning a repository, like npm install.

Options

| Flag | Description | |---|---| | --claude | Setup only Claude Code | | --cursor | Setup only Cursor | | --all | Setup all agents (default) | | --force | Overwrite existing non-symlink files (backs up to .bak) | | --no-generate | Skip AGENTS.md generation |

Migration from existing CLAUDE.md

If the repo already has a CLAUDE.md (not a symlink) and no AGENTS.md, the tool will:

  1. Copy CLAUDE.md content into AGENTS.md
  2. Replace CLAUDE.md with a symlink to AGENTS.md

Windows

On Windows, directory symlinks are created as junctions (no admin rights required). File symlinks (CLAUDE.md) require Developer Mode or administrator privileges.

How it works

  1. Creates .agents/rules/ and .agents/skills/ if they don't exist
  2. Adds generated paths to .gitignore
  3. Generates AGENTS.md (or migrates from existing CLAUDE.md)
  4. Creates symlinks for each agent:
    • Claude Code: CLAUDE.md → AGENTS.md, .claude/rules → .agents/rules, .claude/skills → .agents/skills
    • Cursor: .cursor/rules → .agents/rules