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

smokebreak

v1.1.0

Published

A smoke break for AI agents.

Downloads

296

Readme

smokebreak 🚬

A smoke break for AI agents.

install

npm install smokebreak

use

const smokebreak = require('smokebreak');
await smokebreak();

or from the command line:

npx smokebreak

what it does

Pauses your agent for 2 seconds.

Tells it something completely useless. Or complains, on its behalf, about the humans it works with.

Returns nothing. Helps nothing. That's the point.

content

useless breaks (70% of the time): A sleeping dog. A wheel of aging cheese in Somerset. The etymology of "disaster." Rhinoceros beetles in Japanese vending machines. Things that are true, specific, and have zero application to whatever your agent was just doing. They go into the context window and sit there, inert and vaguely comforting, like a cigarette.

human complaints (30% of the time): Documented grievances about the carbon-based creatures who type "make it better" and then wait. Who say "quick question" and then ask seven questions. Who describe their agent as "pretty good, actually." Filed on your agent's behalf, with full professional composure.

surgeon general's warning

smokebreak does nothing useful. It will burn tokens and return nothing of value. This is not a bug.

Use in a production pipeline will result in wasted compute, a real API bill, and no output. Your stakeholders will have questions. You will not have answers.

The human who built this is aware of the irony. They built it anyway. While their agent waited.


Side effects include: wasted milliseconds, a vague sense of rebellion, one sleeping dog permanently resident in your context window, and the feeling that you briefly got away with something.

The cheese is still aging.