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

@averspec/agent-plugin

v0.1.3

Published

Agent plugin for Aver — workflow skills + GitHub Issues scripts

Readme

@averspec/agent-plugin

Status: Experimental — API may change between minor versions.

Agent plugin for Aver — domain-driven acceptance testing.

What's Included

  • Skillsaver-workflow facilitates scenario mapping and domain design (5-stage pipeline: captured → characterized → mapped → specified → implemented). telemetry augments the workflow with OTel observability patterns.
  • Scripts — Bash scripts for managing scenarios and backlog items, with pluggable backends (GitHub Issues or Linear).

Installation

Register the plugin in .claude/settings.json:

{
  "permissions": {
    "allow": ["Bash(packages/agent-plugin/scripts/gh/*)"]
  }
}

Backend Setup

The plugin supports two backends for scenario and backlog tracking. Set AVER_BACKEND to choose (defaults to gh).

GitHub Issues (default)

Requires the gh CLI authenticated:

gh auth status

Run label setup once per repository:

packages/agent-plugin/scripts/gh/setup-labels.sh

Linear

Run the interactive setup:

npx @averspec/agent-plugin setup

This will:

  1. Prompt for your Linear API key
  2. Let you select your team
  3. Save credentials to ~/.config/aver/.env
  4. Optionally create the required labels in Linear

Manual setup: Create ~/.config/aver/.env (or .env in your project root):

LINEAR_API_KEY=lin_api_...
LINEAR_TEAM_ID=YOUR_TEAM_KEY

Credential lookup order: environment variables → .env in cwd → ~/.config/aver/.env.

Update your Claude settings to allow Linear scripts:

{
  "permissions": {
    "allow": ["Bash(packages/agent-plugin/scripts/linear/*)"]
  }
}

Usage

Once installed, Claude Code can:

  1. Follow the scenario mapping workflow when adding features
  2. Manage scenarios and backlog items via scripts
  3. Use /aver:aver-workflow to invoke the skill directly

Scripts

Both backends expose the same script interface.

Scenario Scripts

| Script | Description | |--------|-------------| | scenario-capture.sh | Capture a new scenario | | scenario-list.sh | List scenarios, filter by stage or keyword | | scenario-get.sh | Get full details for a scenario | | scenario-advance.sh | Move scenario to the next pipeline stage | | scenario-question.sh | Attach an open question to a scenario | | scenario-resolve.sh | Mark a question as resolved |

Backlog Scripts

| Script | Description | |--------|-------------| | backlog-create.sh | Create a new backlog item | | backlog-list.sh | List backlog items with filters | | backlog-update.sh | Update labels, title, or body | | backlog-close.sh | Close a backlog item |

Setup Scripts

| Script | Description | |--------|-------------| | setup-labels.sh | Create required labels (idempotent) | | setup.sh (Linear only) | Interactive credential + label setup |

Requirements

  • Node.js >= 22
  • GitHub backend: gh CLI authenticated (gh auth status)
  • Linear backend: Linear API key (create one here)