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

@pzy560117/opentest

v0.1.9

Published

OpenTest quality evidence lifecycle skills for Codex

Readme

OpenTest

OpenTest is a Codex skill bundle for planning, running, verifying, and archiving quality evidence for code changes.

It is intended for OpenTest-driven development: before implementation, it turns explicit requirements plus implicit product behavior into an acceptance-to-test matrix, then uses that matrix to drive unit, component, integration, contract, E2E, smoke, browser acceptance, and security evidence.

It provides a small lifecycle:

plan -> author -> run -> accept -> verify -> archive

heal is a recovery phase for stale test assets and must not hide product behavior failures.

When OpenTest needs code-level tests and the project does not declare an existing test framework, it defaults to pytest. Coverage completeness is enforced through the acceptance-to-test matrix: every applicable behavior, boundary, and risk surface must have evidence or an explicit gap/blocker with a recovery path.

Recommended placement in a development loop:

requirement / design
  -> opentest plan
  -> opentest author
  -> implementation
  -> opentest run
  -> opentest accept
  -> opentest verify

Install

Install the package, then run the initializer from any project:

npm install -g @pzy560117/opentest
opentest init

opentest init lets you choose the target tool, language, project/global scope, and project path. This is the recommended path for Claude Code, Codex, Cursor, OpenCode, Gemini CLI, Qwen Code, and Qoder users.

You can still run fully scripted installs. For example, install Chinese OpenTest skills for Claude Code in the current project:

opentest install --scope project --platform claude --language zh

Install Chinese OpenTest skills for Qoder in a specific project:

npx @pzy560117/opentest install --scope project --platform qoder --language zh --project /path/to/project

Install Chinese OpenTest skills globally for Codex:

npx @pzy560117/opentest install --scope global --platform codex --language zh

Legacy global install with overwrite:

npx @pzy560117/opentest install --global --force

Legacy project install with overwrite:

npx @pzy560117/opentest install --project /path/to/project --force

Install Options

| Option | Meaning | Default | | --- | --- | --- | | --scope <project|global> | Install into the selected project skills directory or the user's global skills directory. | project | | --platform <id> | Target AI programming tool. Supported IDs are listed below and are read by the CLI from assets/manifest.json. | codex | | --language <en|zh> | Skill language to install. en installs English skills; zh installs Chinese skills. | en | | --project <path> | Project root used for project-scope installs. This also selects project scope for legacy compatibility. | Current working directory | | --global | Legacy alias for --scope global --platform codex. | Disabled | | --force | Overwrite existing manifest-managed OpenTest skill directories. | Disabled |

Supported Platforms

The CLI reads platform data directly from the package manifest at assets/manifest.json; the paths below are shown using project-relative and home-relative notation.

| Platform ID | Tool | Project skills directory | Global skills directory | | --- | --- | --- | --- | | codex | Codex | .codex/skills | ~/.codex/skills | | claude | Claude Code | .claude/skills | ~/.claude/skills | | cursor | Cursor | .cursor/skills | ~/.cursor/skills | | opencode | OpenCode | .opencode/skills | ~/.config/opencode/skills | | gemini | Gemini CLI | .gemini/skills | ~/.gemini/skills | | qwen | Qwen Code | .qwen/skills | ~/.qwen/skills | | qoder | Qoder | .qoder/skills | ~/.qoder/skills |

When adding a platform, update at least assets/manifest.json and scripts/smoke-test.js in this package so the installer data and smoke coverage stay in sync. Update this README table in the same change.

Restart the target AI programming tool or open a new session after installation so the new skills are loaded.

Included Skills

  • opentest
  • opentest-plan
  • opentest-author
  • opentest-run
  • opentest-accept
  • opentest-verify
  • opentest-heal
  • opentest-archive

Package Contents

  • assets/skills/: English skill files
  • assets/skills-zh/: Chinese skill files
  • assets/manifest.json: published asset manifest
  • bin/opentest.js: installer CLI