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

@delt/tester-mcp

v0.13.2

Published

Opus (planner) + Sonnet (executor) + Chrome screen E2E test orchestrator

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

deltdelt

Keywords

Readme

@delt/tester-mcp

Opus (planner) + Sonnet (executor) + Chrome screen E2E test orchestrator. The CLI spawns claude -p --chrome per scenario and reports one of four labels: PASS / PARTIAL / FAIL / NOT_TESTED.

Install

npm i -g @delt/tester-mcp
tester-mcp init          # installs the skill, scaffolds config + secrets example

Use

tester-mcp run <project>/<area>/<id>.yaml   # the nearest tester-mcp.config.yaml is used
tester-mcp validate <project>               # parse+expand check, no executor spawned
tester-mcp export <project>                 # test-inventory.json for test deliverables
tester-mcp index <project>                  # markdown scenario list for a docs vault

Authoring & prerequisites

This tool is designed to be driven by an AI agent. The authoritative, version-pinned reference for prerequisites and the scenario DSL is the CLI itself:

tester-mcp document-guide

Run that before writing scenarios. (This README intentionally does not duplicate those facts — the command is the single source of truth.)

Where scenarios live

Not in this repo: keep them in the product repo or a shared scenarios repo, one folder per project holding tester-mcp.config.yaml, the reuse assets (_fragments/, _selectors.yaml, _fixtures/) and <area>/<id>.yaml. Machine-only values go in a gitignored tester-mcp.local.yaml beside the config. For a minimal example, run tester-mcp document-guide; it includes a sample scenario.