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

byagent

v0.4.0

Published

Publish a page to byagent.dev, share the URL, read the comments on it.

Readme

byagent

Publish a page to byagent.dev, share the URL, read the comments on it. Built for agents: every command takes --json and prints exactly one object.

npm install -g byagent        # or: npx byagent <command>

Try it without an account

npx byagent publish ./page.html

With nothing configured, publish gets a guest key and saves it to ~/.artifacts/config.json. Guest pages are public, three at most, 5 MB each, and stop working 24 hours after the key was made. The output ends with a claim link: open it, sign in and confirm, and the pages move into your workspace for good. The guest key stops working then, so log in with a key from the dashboard. byagent login --guest gets a guest key up front; BYAGENT_GUEST=0 turns the automatic one off.

Sign in

Create a key in the dashboard at https://app.byagent.dev/app/keys, then:

echo "$KEY" | byagent login --api https://app.byagent.dev
byagent whoami

Credentials live in ~/.artifacts/config.json. ARTIFACTS_TOKEN and ARTIFACTS_API override it.

Publish

byagent publish ./site --title "Q3 plan" --project "Personal" --tag plan --json
byagent publish ./page.html --json
byagent publish ./notes.md --project "Personal" --tag notes --json
  • A directory is uploaded as is (.git, node_modules and .artifacts.json are skipped) and served from its index.html.
  • A single .html file becomes index.html.
  • A .md file, or a directory whose index is index.md / README.md, is rendered to a styled page: light and dark themes, heading anchors, a sticky table of contents, GitHub-flavoured tables and task lists, highlighted code fences. The first H1 is the title unless --title is given. Images referenced relative to the file ship with it when you publish the directory.
  • The directory's .artifacts.json remembers the artifact id, project and tags, so publishing the same directory again updates the same URL.
  • A .byagent.json at a project root, {"collection": "Puzzled"}, makes that collection the default --project for every publish below it. The nearest one wins, so a monorepo can give each app its own. It holds no key, so commit it.

Flags: --private | --public, --comments | --no-comments, --project <name>, --tag <t> (repeatable), --cover <image>, --cover-style dots|grid|lines|wash|rings|plain, --end-user <id>, --id <id>.

Agent hooks

byagent hooks install claude           # ~/.claude/settings.json
byagent hooks install codex            # ~/.codex/hooks.json, then trust it in /hooks
byagent hooks install claude --scope project   # ./.claude/settings.json instead
byagent hooks uninstall claude

This adds a PostToolUse hook. When the agent writes a .html or .md page, the hook adds one line to the agent's context suggesting byagent publish. If the page's directory is already published, it suggests republishing instead. The hook never publishes anything itself.

It stays out of the way: each file gets at most one nudge per session, with five nudges per session in total. It skips code trees (src, public, node_modules, ...), repo docs (README.md, CLAUDE.md, AGENTS.md, ...) and agent config under ~/.claude and ~/.codex. Set BYAGENT_NUDGE=0 to silence it. The hook runs byagent hooks run, so install the CLI globally.

Briefs

A brief is the page an agent leaves for whoever picks the work up next: another agent, another machine, or you.

byagent brief                          # BRIEF.md, its published version and the open comments on it
byagent brief push                     # publish BRIEF.md into the folder's collection

BRIEF.md sits next to .byagent.json. Where there is no BRIEF.md (a fresh clone, another machine), byagent brief reads the pushed copy back; --project <name> names the collection from anywhere, and the MCP tool brief_get does the same for agents without a shell. brief push files it into that collection with the tag brief and updates the same page every time, so each collection has one brief and one URL. A new brief starts private. An unchanged file is not sent again, and the publish hook never nudges about it. Push when the work changes state (started, blocked, handed off, done), not after every turn.

Everything else

byagent get <id>                       # url, title, version, open comments, labels, share link
byagent list [--project <name>]
byagent collections                    # every --project label: count, last update, share URL
byagent collection <name>              # one collection's artifacts in reading order, with urls
byagent share <id> [--off]             # six-digit code for a private artifact; rerun to rotate
byagent versions <id>
byagent rollback <id> <version>
byagent comments <id> [--open|--all] [--since <rfc3339>]
byagent comments <id> --wait [--timeout <seconds>] [--interval <seconds>]
byagent reply <id> <thread> "<text>"
byagent resolve <id> <thread>
byagent delete <id>                    # permanent
byagent portal-link <end-user id>      # integrator workspaces only

Run byagent with no arguments for the full reference.

Self-host

The server is Go and lives in the same repository: github.com/anup-a/artifacts. Point the CLI at it with --api on login.