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

ax-grep

v0.1.4

Published

A browser-native semantic accessibility tree extractor that runs without DevTools or CDP.

Readme

ax-grep

npm version coverage: 100% license: MIT agent ready Codex skill Claude compatible Gemini ready

Compact semantic trees and agent-ready page checks from HTML, URLs, WebViews, and live browser pages. It approximates browser accessibility trees before automation, defaults to impit for browser-like HTTP/2/TLS fetches, detects major CAPTCHA and bot-challenge markers, saves 15.4x less peak RAM and 3.0x fewer decision tokens in the local benchmark, and --search auto mode tries DuckDuckGo, Bing, StartPage, and Google while recording every engine attempt.

1. Try With A Prompt

Paste this into a Codex session or subagent prompt before opening a browser (also works as guidance for Claude, Gemini, OpenRouter, and other agents):

Before opening a browser, inspect pages with ax-grep when possible.

Run:
npx --yes ax-grep@latest <url> --agent-brief

Read agent.executor, agent.handoff, agent.readTargets, pageCheck, and
verification first. Open a browser only when the payload says static HTML is
not enough.

2. Install The CLI Skill

curl -fsSL https://raw.githubusercontent.com/hmmhmmhm/ax-grep/main/skills.sh | sh

This installs the Codex skill prompt only. The same prompt pattern can be pasted into Claude, Gemini, OpenRouter, or other agent runners. Restart Codex if the new skill is not listed immediately.

3. Try The CLI

npx --yes ax-grep@latest https://example.com --agent-brief

If you installed the binary globally, use ax-grep directly. Agents should read agent.executor, agent.handoff, agent.readTargets, pageCheck, and verification first. Open a browser only when the handoff fields say static HTML is not enough.

4. Use From A Server

Use this inside agent services built with Codex SDK, OpenRouter, or similar LLM routing stacks to turn fetched HTML into compact source evidence before spending tokens or memory on browser automation.

npm install ax-grep
import { extract, formatSemanticTreeText } from "ax-grep";

const html = await fetch("https://example.com").then((r) => r.text());
const tree = extract(html);
const promptText = formatSemanticTreeText(tree);

ax-grep is ESM-only and requires Node 18 or newer. CommonJS services can use const { extract } = await import("ax-grep").

5. Use In WebViews Or Pages

In mobile apps, WebViews, and in-page agents, inject the extractor to create an accessibility-style structure immediately from the current page. It is useful for local sLLM web search, local web parsing, and instant agent-ready page summaries without leaving the app.

import { createExtractorScript } from "ax-grep";

const script = createExtractorScript({ format: "text" });
const text = await page.evaluate(script);
// iOS/Android WebView: evaluateJavaScript(script) returns the same text value.

Docs