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

@horiastanxd/agentsmd

v0.1.0

Published

Generate an AGENTS.md for your project by scanning config files and extracting commands

Readme

agentsmd

CLI that generates an AGENTS.md for your project. It reads your existing config files — package.json, pyproject.toml, Cargo.toml, go.mod, and others — and produces a ready-to-fill template with detected commands, linters, and project structure.

AGENTS.md is the file AI coding agents (Claude Code, Codex, Cursor, Gemini CLI, and others) read to understand how to work in a repo.

Usage

npx agentsmd

Or install globally:

npm install -g agentsmd
agentsmd

By default it writes AGENTS.md in the current directory. Pass a path to run it elsewhere:

agentsmd ./my-project

Options

| Flag | Description | |------|-------------| | --output <file> | Write to a different file name | | --stdout | Print to stdout instead of writing | | --overwrite | Overwrite an existing AGENTS.md | | --version | Print version | | --help | Print help |

What it detects

| Ecosystem | Files read | Extracted | |-----------|-----------|-----------| | Node.js | package.json, lock files | scripts, package manager, framework, linters | | Python | pyproject.toml, requirements.txt, Pipfile, poetry.lock, uv.lock | package manager, test runner, linters | | Rust | Cargo.toml | build/test/lint commands, workspace flag | | Go | go.mod, .golangci.yml | module name, build/test/lint commands | | Ruby | Gemfile | bundler, rspec/rake, RuboCop | | Java/Kotlin | pom.xml, build.gradle | Maven or Gradle commands | | PHP | composer.json | composer install, PHPUnit |

For multi-language monorepos, sections for each detected ecosystem are included.

Output example

Running agentsmd --stdout on a typical Next.js project:

# AGENTS.md

Instructions for AI coding agents working in this repository.

## Setup

    npm install

## Commands

- **build**: `npm run build`
- **dev**: `npm run dev`
- **test**: `npm run test`
- **lint**: `npm run lint`

## Code style

Linters / formatters in use: ESLint, Prettier, TypeScript

## Architecture

Framework: Next.js

_Fill in component boundaries, data flow, and any non-obvious constraints here._

## Conventions

_Add project-specific conventions: naming, file organisation, commit format, etc._

Why

Most repos that work with AI agents need some form of AGENTS.md (or CLAUDE.md, .cursorrules, etc.) to give the agent context on how to build, test, and lint the code. Writing one from scratch every time is tedious. This tool does the mechanical part — scanning configs — and leaves the judgment calls (architecture, conventions, gotchas) for you to fill in.

Requirements

Node.js 18 or later. No runtime dependencies.

License

MIT