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

dotagents

v0.2.0

Published

Carry your AI-agent skills and setup across machines with a portable, Git-backed library

Readme

A successful dotagents setup

What it does

AI agents store skills in different places. dotagents gives you one library — normally ~/.agents — and safely makes its skills available to the compatible agents already installed on your computer.

| You have | dotagents does | | --- | --- | | A skill in ~/.agents/skills | Keeps it in the shared library; agents that read the shared folder use it directly. | | A compatible agent with an empty skills folder | Creates per-skill links back to the library. No duplicate copy to maintain. | | A non-empty or unfamiliar agent folder | Leaves it alone. It never replaces files it does not manage. | | A skills.sh package with verifiable provenance | Records a pinned source instead of uploading another copy. |

[!IMPORTANT] dotagents setup does not publish anything. It only creates or updates your local ~/.agents library after one confirmation. When you choose to connect GitHub, GitLab, or another Git server, dotagents records only its credential-free remote address on this computer. It creates a remote only if you explicitly select Create a new private library and confirm its exact name; pushing remains a separate dotagents sync confirmation.

Start here

Install the CLI, then run one command:

npm install -g dotagents
dotagents setup

The command shows what it found and asks once before it changes anything. If you want to carry the library elsewhere, choose GitHub, GitLab, or Another Git server and enter that server's Git URL once. After you answer y, it:

  1. creates ~/.agents if necessary;
  2. brings in skills that are safe to own, while retaining verified external sources as references;
  3. connects compatible empty agent folders with links; and
  4. reports exactly what is now available.

Choosing GitHub or GitLab first asks permission to let that provider's own CLI list writable repositories, so you can reuse an existing library without remembering its URL. This is separate from reviewing library content and from creating a remote; automated setup must opt in with --allow-provider-network.

If you install another agent later, run this to connect it without touching existing agent files:

dotagents connect

Check the current connections at any time:

dotagents status

Back up or share your library

After the one-time setup, syncing never asks you to remember a path or remote. It uses the saved library connection on this computer, reviews portable files for secrets, and asks for confirmation before it writes or pushes.

dotagents sync

Choose the repository visibility that fits your use: private for a personal backup, team-accessible for shared work, or public only after you have reviewed its contents. Before using a public remote, run:

dotagents doctor ~/.agents
dotagents audit ~/.agents --public

Secret checks point to a file and line but never print the matched value.

Restore on a new computer

On a new computer, start with dotagents setup. Pick GitHub or GitLab and choose an existing repository, or review a new private library name before dotagents creates it through the provider CLI. For a company or self-hosted server, choose Another Git server and paste its Git URL once; dotagents saves that connection locally and will not ask again. The --remote option remains available for scripts and managed deployments. Before writing ~/.agents, it reviews and pins the exact remote commit, then safely connects compatible agents it finds.

dotagents setup

What dotagents will not do

  • It does not create a remote repository unless you explicitly select and confirm its exact private name; it never makes one public on its own.
  • It does not push until a separate reviewed dotagents sync confirmation.
  • It does not overwrite an existing agent skill or follow a linked file outside a skill folder.
  • It does not silently trust a network source; network operations require an explicit trust rule.
  • It does not run skill code while discovering, reviewing, or copying files.

Need the deeper controls?

The normal route is setupsyncsetup on another computer. For dry runs, automation, recovery, source trust, and the complete command reference, see:

dotagents is open source, provider-neutral, and works with any Git host that you choose.