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

@eddiedao/ai-handoff

v1.0.1

Published

Deterministically hand a GitHub issue to the AI-tunnel bot: verify plan pushed to the default branch, set the plan marker in the issue body, then apply the trigger label last. A Claude Code skill + CLI.

Readme

@eddiedao/ai-handoff

A Claude Code skill and CLI that deterministically hands a GitHub issue to an AI-tunnel bot for autonomous implementation.

It enforces, in order, the contract such bots require:

  1. the plan is committed & pushed to origin/<default-branch>;
  2. a <!-- plan="plans/<slug>/" --> marker is present in the issue body;
  3. the trigger label (AI handle) is applied last (fires the labeled webhook).

Verify-before-label + idempotent, so a completed/running issue is never accidentally re-triggered (which would open a duplicate PR).

Install

npm install -g @eddiedao/ai-handoff

postinstall copies the skill into ~/.claude/skills/ai-handoff/ so Claude Code discovers it, and installs an ai-handoff command on your PATH. To (re)install the skill files manually:

ai-handoff-install

Requirements: Node >= 18, git, and an authenticated gh with push + issue write access. macOS/Linux (the CLI is a bash script).

Usage

From inside the repo (auto-cd to repo root):

ai-handoff [--force] <issue-number> [plan-path]
  • plan-path optional — auto-resolved from plans/*/plan.md frontmatter issue: <N>.
  • --force re-triggers even when the issue is already AI in progress / AI done.
  • Label overrides via env: TRIGGER_LABEL, PROGRESS_LABEL, BLOCKED_LABEL, DONE_LABEL.

Recommended flow: ak:plan → ak:git cp (push plan to default branch) → ai-handoff <issue>.

Fire-and-forget: the handoff is complete once the trigger label is applied. The tool does not poll, wait on, or monitor the bot — it dispatches and exits. Track progress yourself with gh issue view <N> / gh pr list when you choose.

What it does NOT do

Bot-independent by design — it only touches GitHub issue state and the git remote. It does not run, host, or know where the bot runs. It does not implement the issue. It does not monitor or poll the bot after dispatch — once the trigger label is applied it exits, leaving progress tracking to you.