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

@021.is/agent-docs

v0.1.2

Published

Single-source-of-truth docs catalog + .md route handlers + llms.txt + agent-prompt scaffolding. One library, every product gets first-class agent integration.

Readme

@021.is/agent-docs

Single-source-of-truth docs catalog. One library, every product gets first-class agent integration without copy-paste.

One DocsCatalog object feeds:

  • the JSX page (your existing app/docs/<slug>/page.tsx)
  • the .md route handler (drop in markdownRoute(catalog))
  • the /llms.txt discovery index (buildLlmsTxt)
  • the /llms-full.txt flat dump (buildLlmsFullTxt)

Drift between surfaces becomes physically impossible.

Install

bun add @021.is/agent-docs

Quickstart

Define one catalog per page in lib/docs/<slug>.ts:

import { type DocsCatalog, code, h2, p } from "@021.is/agent-docs";

export const installCatalog: DocsCatalog = {
  slug: "install",
  title: "Install the SDK",
  description: "One package, two minutes to working sign-in.",
  body: [
    h2("Install"),
    p("Use your package manager."),
    code("bash", "bun add @021.is/my-sdk"),
  ],
};

Drop the matching .md route handler:

// app/docs/install.md/route.ts
import { markdownRoute } from "@021.is/agent-docs/next";
import { installCatalog } from "@/lib/docs/install";

export const dynamic = "force-static";
export const GET = markdownRoute(installCatalog);

Wire llms.txt:

// app/llms.txt/route.ts
import { llmsTxtRoute } from "@021.is/agent-docs/next";
import { installCatalog } from "@/lib/docs/install";

export const dynamic = "force-static";
export const GET = llmsTxtRoute({
  name: "my-app",
  tagline: "Your product tagline.",
  siteUrl: "https://example.com",
  catalogs: [installCatalog],
  openapi: { yamlUrl: "https://example.com/openapi.yaml" },
});

That is the whole integration. Every catalog you ship is automatically rendered on /docs/<slug>.md, listed on /llms.txt, and concatenated into /llms-full.txt.

Why

Stripe, Auth0, and Clerk all ship agent-consumable docs. So do we. Reuse the library and your product is on day one.

License

MIT.