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

@zinokhedri/manual-tester

v1.0.1

Published

Chrome-based manual testing skill for AI coding tools. Checkpoint architecture prevents context limit exhaustion during long test runs.

Readme

manual-tester

A manual testing skill for AI coding tools. Uses a checkpoint architecture to prevent context limit exhaustion during long browser test runs.

The Problem

Manual testing in AI cowork sessions hits context limits quickly. Every browser interaction — screenshots, DOM snapshots, network logs — adds 10,000–50,000 tokens. After 10 steps, the session is saturated.

The Solution

Every test step runs inside an isolated subagent. The subagent handles all browser interactions in its own disposable context and returns only a compact checkpoint summary (~100 tokens) to the main session. A 50-step test run uses ~5K tokens in the main context instead of 500K+.


Installation

Via npx (recommended)

npx @zinokhedri/manual-tester

Automatically detects and installs to all supported tools found on your machine.

Via npm (global)

npm install -g @zinokhedri/manual-tester
manual-tester

Supported Tools

| Tool | Install location | |------|-----------------| | Claude Code | ~/.claude/skills/manual-tester/ | | Cursor | ~/.cursor/rules/manual-tester.mdc | | Windsurf | ~/.codeium/windsurf/memories/manual-tester.md | | GitHub Copilot | .github/copilot-instructions.md (project-level) |

Restart your AI tool after installation to activate the skill.


Usage

/manual-tester                        Full interactive intake
/manual-tester https://myapp.com      Skip URL question
/manual-tester --report               Regenerate report from existing checkpoints
/manual-tester --rerun                Re-run only FAIL/BLOCKED steps

How It Works

Phases

| Phase | What happens | Output | |-------|-------------|--------| | 0. Intake | URL, flows to test, credentials, final delivery method | — | | 1. Plan | Auto-generates numbered test steps, user confirms before running | TEST_PLAN.md | | 2. Execute | Each step runs in an isolated subagent via the Agent tool | CHECKPOINTS.md + screenshots | | 3. Report | Compiles results, delivers via chosen method | TEST_REPORT.md |

Output Structure

Each run creates a timestamped directory in your current working directory:

test-results/<ISO-timestamp>/
├── TEST_PLAN.md          # Confirmed test plan
├── CHECKPOINTS.md        # Live checkpoint log
├── TEST_REPORT.md        # Final report with pass/fail summary
└── screenshots/
    ├── step-1-before.png
    ├── step-1-after.png
    └── ...

Final Delivery Options

  • Save to fileTEST_REPORT.md written to the results directory
  • Email — Drafted and sent via Gmail MCP
  • Slack — Summary posted to a channel via Slack MCP
  • Inline — Report printed in the conversation

File Structure

manual-tester/
├── package.json
├── LICENSE
├── README.md
├── SKILL.md                          # Main skill definition
├── bin/
│   └── install.js                    # npx install script
├── .claude-plugin/
│   └── plugin.json                   # Claude Code plugin manifest (alternative install)
├── agents/
│   └── step-executor.md              # Isolated subagent prompt for one test step
├── references/
│   ├── intake-questions.md           # Intake question set
│   ├── checkpoint-format.md          # CHECKPOINTS.md column spec
│   └── test-plan-format.md           # TEST_PLAN.md row format
└── templates/
    ├── TEST_PLAN.md
    ├── CHECKPOINTS.md
    └── TEST_REPORT.md

Publishing to npm

cd skills/manual-tester
npm publish --access public

Users can then install with:

npx @zinokhedri/manual-tester

License

MIT