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

@h4pplness/agent-wiki

v1.0.3

Published

CLI knowledge base platform for AI agents, organized by domain

Readme

agent-wiki

A minimal CLI knowledge base for AI agents, organized by domain.

No server. No authentication. Just Markdown files and a lightweight CLI.

Install

npm install -g @h4pplness/agent-wiki

Quick start

# Create a domain
agent-wiki my-project init --desc "Backend API project. Stores architecture, API contracts, and technical decisions."

# Read the schema before doing anything else
agent-wiki my-project schema

# Write a page
agent-wiki my-project write wiki/overview.md "# Overview

> High-level description of the system architecture and key components.

---

Content here."

# View a page
agent-wiki my-project view wiki/overview.md

# Update part of a page with a patch
agent-wiki my-project patch wiki/overview.md --file ./change.diff

# Example change.diff:
# @@
# -Content here.
# +Three services: auth, product, order.

# List all pages
agent-wiki my-project list

# List all domains
agent-wiki domains

Commands

| Command | Description | |---|---| | agent-wiki <domain> init --desc "<desc>" | Create a new domain | | agent-wiki <domain> schema | View schema and domain description | | agent-wiki <domain> schema edit "<content>" | Overwrite the schema | | agent-wiki <domain> view <path> | View a file | | agent-wiki <domain> write <path> "<content>" | Create or overwrite a file | | agent-wiki <domain> patch <path> --file <patch-file> | Apply a unified-diff style patch to a file | | agent-wiki <domain> list [path] | List wiki files | | agent-wiki <domain> delete --confirm | Delete a domain | | agent-wiki domains | List all domains |

Patch format

patch applies simple unified-diff style hunks. Use a space for context lines, - for removed lines, and + for added lines.

@@
 - [agent-wiki](wiki/projects/agent-wiki.md) - CLI knowledge base
+- [confluence-cli](wiki/projects/confluence-cli.md) - CLI tool

In the example above, the first line starts with a space before the Markdown -. That keeps the existing list item as context and inserts the new list item after it.

Data location

All data is stored locally at ~/.agent-wiki/. Override with the AGENT_WIKI_DIR environment variable.

~/.agent-wiki/
└── domains/
    └── my-project/
        ├── meta.json
        ├── schema.md
        └── wiki/
            └── index.md

Page format

Every wiki page must start with a purpose block:

# Page Title

> What this page is about, what is stored here, and when to read it.

---

Pages without a purpose block are considered invalid.

License

MIT