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

@intentic/webq

v1.378.1

Published

webq, agent-native web fetch CLI: any URL as clean budgeted markdown, and bounded same-site crawls, over one shared cache

Downloads

9,842

Readme

webq

A CLI that fetches web pages for an agent as pruned, token-budgeted markdown and crawls a site into files, over one shared cache.

flowchart LR
    agent["Agent<br/>webq fetch · crawl"] --> webq(["webq"])
    webq --> cache["Shared cache<br/>per URL and render mode"]
    webq --> http["Static HTTP"]
    webq --> chromium["Headless Chromium<br/>empty app shells"]
    webq --> out["Capsule on stdout<br/>whole page saved"]
  • A raw page is mostly navigation and script, and one docs page can fill a context window. webq fetch prints a capsule (title, final URL, token cost, cache, network or browser), then the page with its chrome pruned and clipped to --budget, and saves the whole page as markdown with front matter.
  • --query keeps only the blocks relevant to a question (BM25). On a crawl it also visits matching links first.
  • When the static HTML is an empty app shell, the page renders in the image's Chromium if that feature pack is installed; without it webq says so and serves the static HTML.
  • Crawls stay on the start origin, obey robots.txt and report every skipped URL by reason, so a capped crawl never reads as complete.
  • The sandbox image puts webq on PATH and loads plugin/skills/webq/SKILL.md, which tells agents when to use it over WebFetch. It does not handle pages behind a sign-in. fileq reuses the ./dom and ./markdown exports for HTML-based documents.

Usage

webq fetch https://docs.example.com/guide --query "rate limits"
webq crawl https://docs.example.com --max-pages 30

Key files

Commands

pnpm --filter @intentic/webq test