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

agents-md-link

v0.1.2

Published

Manage your global AGENTS.md in one place.

Readme

agents-md-link

Manage your global AGENTS.md in one place. User-level only: it never reads or writes project-level AGENTS.md, CLAUDE.md or GEMINI.md.

  • Source: ~/.agents/AGENTS.md
  • Config: ~/.agents/agents-link.json
  • Backups: ~/.agents-md-link/backups/

What it does

  • Keeps a single source at ~/.agents/AGENTS.md; tool config files point to it.
  • Prefers symlinks and falls back to hardlinks on Windows without Developer Mode.
  • Never silently overwrites an existing rule file: it backs up first and asks you to pick a base when files differ.
  • Shows status, repairs broken links, and removes targets.

Quick start

npm install -g agents-md-link
agents-md-link install

From a clone, use npm install -g . and run node bin/agents-md-link.js install.

install shows a checkbox list of supported tools. Use ↑/↓ to move, Space to toggle, a for all, n for none, Enter to confirm, Esc to cancel. Detected tools are selected by default. After confirmation it creates the source, backs up existing files, and links the selected targets.

Commands

| Command | What it does | |---|---| | agents-md-link install | Select tools, install or migrate (alias: add) | | agents-md-link status | Show every target, extra rules and cross-read hints | | agents-md-link link | Repair missing targets, broken links and stale copies | | agents-md-link uninstall | Select installed targets and remove them |

Normal use needs no flags. Flags are for scripts and skills:

agents-md-link install -a claude,codex --yes
agents-md-link status --json
agents-md-link uninstall -a copilot --yes

Targets

| Name | User-level path | |---|---| | claude | ~/.claude/CLAUDE.md | | codex | ~/.codex/AGENTS.md | | gemini | ~/.gemini/GEMINI.md | | copilot | ~/.copilot/copilot-instructions.md | | qoder | ~/.qoder-cn/rules/agents-md-link.md | | opencode | ~/.config/opencode/AGENTS.md (not selected by default) |

Other files under ~/.qoder-cn/rules/, ~/.claude/rules/ and ~/.copilot/instructions/ are not managed. status lists them and reports duplicate-rule when a file is identical to the source. A non-empty ~/.qoder-cn/AGENTS.md is also listed as an extra source.

Link modes

  • auto: try a symlink, then fall back to a hardlink.
  • symlink: symlink only; requires Developer Mode on Windows.
  • hardlink: hardlink only; no elevation, but an editor's atomic save can break it.
  • copy: a managed whole-file copy with a generated header; not instant, run link after editing the source.
agents-md-link install -a claude --mode hardlink --yes

install --mode is saved to the config and reused by link. If status shows detached, run agents-md-link link and choose "Back up and relink", or run agents-md-link link --relink --yes.

Existing content

On first install, selected tools may already have rule files:

  • One non-empty file: ask whether to use it as the shared source.
  • Multiple non-empty files with different content: stop, list them, and ask for a base with --from <path> or a manual merge into ~/.agents/AGENTS.md.
  • Source already exists: the source wins; for each target with content, ask "Back up and replace", "Skip", or "Use this target as the source".

Different files are never concatenated automatically. Every migration, overwrite and relink is backed up first.

Duplicate loading

  • Claude: loads both ~/.claude/CLAUDE.md and ~/.claude/rules/*.md; identical rules duplicate context.
  • Qoder: the desktop app loads ~/.qoder-cn/rules/*.md; this tool puts the shared rule in agents-md-link.md. Qoder CLI may also read ~/.qoder-cn/AGENTS.md. Qoder does not read CLAUDE.md by default.
  • Copilot: reads its own file and may also read ~/.claude/CLAUDE.md and ~/.gemini/GEMINI.md. The official client removes identical copies; verify with /instructions.
  • OpenCode: reads ~/.claude/CLAUDE.md through its compatibility layer, so the OpenCode target is off by default to avoid a second copy.
  • Codex: if ~/.codex/AGENTS.override.md exists, our AGENTS.md is ignored; status marks it as shadowed.

Project-level files are outside this tool. If a repo repeats global rules, each tool still loads both.

Development

npm test

Zero runtime dependencies, Node.js 20+, ESM.

Releasing

Bump version in package.json and commit, then tag and push:

git tag v0.1.2
git push origin v0.1.2

The tag triggers .github/workflows/publish.yml, which publishes to npm through trusted publishing.

Optional skill

skills/agents-md-link/ is a thin, manually invoked skill that calls the repository CLI. From the repository root, install it with a junction (PowerShell, no admin required):

New-Item -ItemType Junction `
  -Path "$env:USERPROFILE\.agents\skills\agents-md-link" `
  -Target "$PWD\skills\agents-md-link"

Then run node run.js status or node run.js install ... from the skill directory. Copying the skill directory instead of using a junction breaks run.js because it resolves the repository bin by relative path.