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

lp-web-search

v1.1.0

Published

A loopengine ability: a web_search tool (Tavily or Brave Search) plus a skill teaching an agent when and how to use it.

Readme

lp-web-search

A loopengine ability: tools for searching and reading the public web, plus a skill that teaches an agent when to reach for each and how to use the results honestly.

What's in it

  • Tool — web_search(query, max_results?). Calls Tavily if TAVILY_API_KEY is set, else Brave Search if BRAVE_API_KEY is set, else Firecrawl's /search if FIRECRAWL_API_KEY is set. Returns { answer, results: [{ title, url, snippet }] } — answer is a short synthesized answer (Tavily only; null on Brave/Firecrawl), results is a ranked list with each snippet trimmed to 500 characters.
  • Tool — web_fetch(url). Fetches a single page (typically a web_search result) and returns its readable text, trimmed to ~8000 characters — for when a snippet isn't enough. Prefers Tavily's Extract API if TAVILY_API_KEY is set, else Firecrawl's /scrape if FIRECRAWL_API_KEY is set (both do real, browser-grade extraction), else a plain fetch with a regex-based HTML-to-text fallback that needs no API key at all. Refuses non-http(s) URLs and local/private-network addresses outright, regardless of backend.
  • Skill — web-search: when to search vs. fetch vs. rely on context or another tool, how to phrase a query, and how to use results without overstating confidence in them.
  • actauth rules — web-search-allowed and web-fetch-allowed, both decision: allow — read-only, no side effect, so neither is left to whatever default_decision an agent has.

Install

npx loopengine add-ability lp-web-search --agent <your-agent>

(or a specific version: npx loopengine add-ability [email protected] --agent <your-agent>)

Then set at least one of these env vars (via the Admin UI's Environment tab, or directly in .env):

TAVILY_API_KEY=...
# or
BRAVE_API_KEY=...
# or
FIRECRAWL_API_KEY=...

None are required for web_fetch to work at all — it falls back to a plain fetch with no API key — but web_search needs at least one of the three. Tavily is preferred if more than one is set.

Upgrading

npx loopengine upgrade-ability lp-web-search --agent <your-agent>

See loopengine's own ABILITIES.md for how abilities, installs, and upgrades work in general — this ability doesn't do anything a hand-written tool couldn't; it's just one someone else already wrote and tested.