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

prompt-inbox

v1.0.0

Published

Remote prompt inbox for the coding agent — static web UI to submit prompts via GitHub Pages

Readme

🎯 Prompt Inbox

Remote prompt inbox for the coding agent (Bartosz Osiej's AI assistant).

  • Page: https://bartoszosiej.github.io/prompt-inbox/ — mobile-first form. Pick a project, type a prompt, submit → GitHub opens with a pre-filled issue (no tokens, no backend — the user just taps "Submit new issue").
  • Inbox: every prompt lands here as a GitHub issue. The page simply pre-fills issues/new?title=…&body=….
  • Repo map: all projects live under github.com/BartoszOsiej; see the Docs registry.

🧭 Agent instructions (for the coding agent)

When the user says something like "check the inbox" (or any new task):

  1. Read open issues from this repo (public — no auth needed): https://api.github.com/repos/BartoszOsiej/prompt-inbox/issues?state=open
  2. Each issue has: title [Project] summary, body with the prompt, optional context and the project/repo.
  3. Handle the prompt in the relevant project repo, then close the issue (and optionally leave a comment with a summary). Closing/commenting requires the user's GitHub token (see projects/github-token.md in the working copy — ask the user before using it).
  4. Reply to the user in the chat with what was done.

Form behaviour

  • index.html is a single self-contained static page (no build step).
  • Submit opens a pre-filled new-issue URL in a new tab: https://github.com/BartoszOsiej/prompt-inbox/issues/new?title=[Projekt] …&body=…
  • The issue title is [Project] <first 60 chars of the prompt>; the body contains the full prompt, project, optional context, timestamp and a note telling the agent to close the issue after handling it.

Re-deploying

Pages is configured to publish from the main branch, / (root) — no Actions workflow needed. Push to main and the site updates automatically.