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

@agent-mokugyo/hooks

v0.1.0

Published

Auto-knock the mokugyo when Claude Code / Codex completes a meaningful task

Readme

@agent-mokugyo/hooks

Auto-knock the mokugyo desk companion when Claude Code / Codex finishes meaningful work.

One command installs a Stop hook into your Claude Code / Codex settings. When the Agent completes a task that involved real tool use (file edits, code execution, etc.), the hook automatically sends a knock to the Mokugyo backend — driving the physical desk-cat device or simulator.

Pure chat responses (no tool use) are silently ignored.

Install

npx @agent-mokugyo/hooks install

This injects a Stop hook entry into ~/.claude/settings.json.

Uninstall

npx @agent-mokugyo/hooks uninstall

Configuration

Set these environment variables (all optional):

| Variable | Default | Description | |----------|---------|-------------| | MOKUGYO_BACKEND_URL | http://localhost:8080 | Mokugyo backend HTTP address | | MOKUGYO_DEVICE_ID | desk-cat-001 | Target device ID | | MOKUGYO_TOKEN | — | Bearer token if backend requires auth |

How It Works

  1. Claude Code finishes responding → fires the Stop hook
  2. on-stop.mjs reads the hook context (stdin JSON with transcript_path)
  3. Parses the JSONL transcript to find the last assistant turn
  4. Counts tool_use blocks — if > 0, the Agent did meaningful work
  5. POSTs a knock to the backend (count scales with tool uses, max 8)
  6. If backend is unreachable, silently exits (never blocks Claude)

Knock Behavior

| Tool uses | Count | Pattern | Intensity | |-----------|-------|---------|-----------| | 1–2 | 1–2 | single | normal | | 3–4 | 3–4 | short-short-long | normal | | 5–8 | 5–8 | short-short-long | strong |

Requirements

  • Node.js 18+ (for native fetch)
  • Claude Code or Codex (provides the hooks infrastructure)
  • Mokugyo backend running at MOKUGYO_BACKEND_URL (see agent-mokugyo for setup)

License

MIT