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

@noppu-labs/opencode-investigate

v0.2.1

Published

Investigation skills: a deterministic structural brief, a deep two-pass investigation, and claim-by-claim spec review

Readme

Investigate toolkit

Investigation skills, installed as the investigate plugin of this marketplace (/plugin install investigate@ai-toolkit, or npx skills add noppu-labs/ai-toolkit/investigate for other harnesses).

| Skill | Purpose | | --- | --- | | investigate:brief | Computes a structural brief for a path before anyone reads code: callers, wiring, blast radius, installed third-party versions, and version-checked doc sources. No LLM is involved. | | investigate:deep | The full investigation of a service, module, or feature. It builds the brief, runs two independent passes from it, and trusts their intersection. | | investigate:spec | Reviews a spec, ticket, or plan claim by claim against the codebase, using the same brief and two passes. |

Claude Code

/plugin marketplace add noppu-labs/ai-toolkit
/plugin install investigate@ai-toolkit

Skills are namespaced after install, for example investigate:brief.

OpenCode

The same skills ship as the OpenCode plugin @noppu-labs/opencode-investigate, also published unscoped as opencode-investigate. It targets OpenCode V2.

Install it with the plugin command, or list it under plugins in your OpenCode config:

opencode plugin add @noppu-labs/opencode-investigate
{
  "plugins": ["@noppu-labs/opencode-investigate"]
}

Update with opencode plugin update.

Invoke a skill with @investigate-<skill>, for example @investigate-deep, or pick one from /skills. The ids are investigate-brief, investigate-deep, and investigate-spec.

By default the brief sends the names of up to 12 imported, non-dev packages to context7.com, anonymously unless CONTEXT7_API_KEY is set; pass --no-docs to skip that call.

The brief script needs Node 20 or later and git on PATH. Documentation lookups use whatever context7 tool the harness provides and fall back to the installed source when there is none.

npx skills add also reaches OpenCode, but it leaves ${CLAUDE_PLUGIN_ROOT} unresolved, so the npm plugin is the supported route there.