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

@adddog/claude-plugin-pnpm

v0.4.0

Published

Claude Code plugin for pnpm monorepos — agent teams, workspace-aware fixing, changeset shipping

Readme

@adddog/claude-plugin-pnpm

A Claude Code plugin that turns a single prompt into a coordinated multi-agent team — from requirements through implementation. Built for pnpm monorepos.

"as a team, build a cache layer for the API"

That one sentence triggers a full agentic pipeline: requirements gathering, codebase research, research-informed refinement, architecture planning, parallel implementation, code review, and verification — all coordinated by a lead agent with disk-backed artifacts at every step.

The Pipeline

Every team follows the same artifact chain. Each phase reads the previous phase's output from disk — no context window pressure, full traceability.

prompt.md → clarify → explore → present → requirements.md
  → research(findings.md)
  → REFINE LOOP (semi-autonomous, grills with research findings)
  → plan(design.md + team-plan.md)
  → review → spawn → implement → verify

How It Works

| Phase | Agent | What Happens | |-------|-------|-------------| | Persist | lead | Raw user request saved to prompt.md — source of truth for intent | | Clarify | designer | One question at a time, recommended answers, codebase exploration | | Explore | designer | 2-3 approaches with tradeoffs, user picks | | Present | designer | Section-by-section requirement approval | | Write | designer | Synthesizes requirements.md — canonical handoff | | Research | researcher | Deep codebase investigation via CocoIndex + claude-mem + code | | Refine | designer | Semi-autonomous: self-resolves code questions, asks humans only for judgment calls. Cross-references research against requirements. | | Plan | planner | Produces design.md (architecture) + team-plan.md (tasks, ownership, phases) | | Implement | coders | Parallel agents, file-ownership enforced, QB reviews | | Verify | verifier + finisher | Lint, types, tests, cleanup |

Semi-Autonomous Refine

The refine phase is where research meets requirements. After the researcher explores the codebase, the designer:

  • Self-resolves questions answerable by code exploration (no lead round-trip)
  • Returns to lead only for human-judgment questions (scope, priority, preference)
  • Tracks rounds, self-resolved vs human-resolved counts
  • Max 10 rounds (configurable), every round writes to disk
Research found existing cache layer in @scope/utils covering 80% of requirements.
→ Designer self-resolves: "extend existing" instead of "build new"
→ Updates requirements.md inline
→ Asks human: "Should we add TTL support? Recommended: yes, existing pubsub supports it."

Agent Roster

Every agent has explicit tool scoping — researchers can't edit code, reviewers can't write source files.

Planning Phase

| Agent | Role | Tools | |-------|------|-------| | team-designer | Phase-aware requirements (clarify/explore/present/write/refine) | Read, Glob, Grep, Write, Bash | | team-researcher | Codebase investigation, evidence gathering | Read, Glob, Grep, Write, Bash | | team-planner | Architecture + task decomposition | Read, Glob, Grep, Write, Bash |

Execution Phase

| Agent | Role | Tools | |-------|------|-------| | team-coder | Implementation | Read, Write, Edit, Glob, Grep, Bash | | team-reviewer | Code quality review | Read, Glob, Grep, Bash, Write | | team-spec-reviewer | Spec compliance (runs before quality review) | Read, Glob, Grep, Bash | | team-tester | Test strategy + writing | Read, Write, Edit, Glob, Grep, Bash | | team-verifier | Lint, types, knip, tests | Read, Glob, Grep, Bash, Write | | team-auditor | Post-implementation audit + diagnostic logging | Read, Write, Edit, Glob, Grep, Bash | | team-finisher | Remove logs, enforce standards (runs last) | Read, Write, Edit, Glob, Grep, Bash | | team-architect | Deep-dive module analysis (mid-execution) | Read, Glob, Grep, Bash, Write | | team-investigator | Root cause debugging | Read, Glob, Grep, Write, Bash | | team-security-auditor | OWASP security audit | Read, Glob, Grep, Bash, Write | | team-monitor | Team health observer (5+ agent teams) | Read, Glob, Grep, Bash, SendMessage | | quarterback | QA reviewer — read-only by design | Read, Grep, Glob, Bash, SendMessage |

Natural Language Triggers

No special syntax. The lead interprets intent:

| What You Say | What Happens | |-------------|-------------| | "as a team, build X" | Full pipeline: persist → clarify → plan → implement | | "that's clear" / "move on" | Exit clarify → explore approaches | | "option A" / "go with B" | Selection recorded → present requirements | | "approved" / "looks good" | Approve section → next | | "plan it" / "let's plan" | Exit refine → planning | | "skip refine" | Bypass refine, straight to planner | | "as a team (fork), build X" | Fork mode — ~10x cost reduction on parallel agents |

Structured Coordination

Disk-Backed Artifacts

All state lives on disk in team-session/{team-name}/. No in-memory-only state. Agents are stateless — they read previous phases from disk, write their output, return. Context windows don't limit history.

STATUS Protocol

Every agent ends with a structured status:

STATUS: CLEAN                              — done, no issues
STATUS: PARTIAL — completed 3/5 tasks      — progress, more to do
STATUS: ERRORS_REMAINING: 2 in @scope/api  — tried, issues remain
STATUS: BLOCKED — missing API schema       — can't proceed

Interrupt Protocol

Lead can interrupt long-running agents:

INTERRUPT: scope changed
Action: pause | abort | report_status

Agents complete their current atomic operation, write progress to disk, respond with status.

Phase Gating

Phases are sequential. Tasks within a phase run in parallel. blockedBy enforces ordering. QB reviews gate phase transitions.

Skills

| Skill | Purpose | |-------|---------| | team-kit-create | Full pipeline: scope → plan → spawn prompt | | team-kit-clarify | Requirements extraction dispatch guide | | team-kit-explore | Approach exploration dispatch guide | | team-kit-present | Section-by-section design approval | | team-kit-review | Post-plan review checklist | | workspace-fix | Fix lint/types/knip in workspace packages | | changeset | Generate changesets from git diff | | ship | Changeset + knowledge refresh + git workflow | | debug-session | Root cause investigation — single or team escalation | | brainstorm-session | Requirements gathering before implementation |

Fork Mode (Cost Optimization)

For ~10x cost reduction on parallel agents:

export CLAUDE_CODE_FORK_SUBAGENT=1

Children inherit the lead's context via prompt cache. First child pays full price, children 2-N pay ~10%.

"as a team (fork), implement the auth refactor"

Dependencies

This plugin integrates with four open-source tools. Use /third-party-manager to check versions, update, and verify.

| Tool | Purpose | Repo | |------|---------|------| | context-mode | Context window protection via FTS5 | mksglu/context-mode | | claude-mem | Cross-session memory | thedotmack/claude-mem | | caveman | Token-optimized communication | JuliusBrussee/caveman | | cocoindex-code | AST-based code search | cocoindex-io/cocoindex-code |

claude-mem

Cross-session memory and observation capture.

  • Repo: https://github.com/thedotmack/claude-mem
  • Docs: https://claude-mem.ai
npx claude-mem install
# Or: curl -fsSL https://install.cmem.ai/openclaw.sh | bash

cocoindex-code

AST-based semantic code search — 70% token savings vs grep.

  • Repo: https://github.com/cocoindex-io/cocoindex-code
pipx install cocoindex-code
ccc init && ccc index

context-mode

Context window protection via FTS5 knowledge base.

  • Repo: https://github.com/mksglu/context-mode

Installed via Claude Code marketplace.

caveman

Token-optimized communication mode (~75% reduction).

  • Repo: https://github.com/JuliusBrussee/caveman

Installed via Claude Code marketplace. Enable with /caveman full.

Install

# Claude Code marketplace (recommended)
claude plugin add @adddog/claude-plugin-pnpm

# Or npm
npm install -g @adddog/claude-plugin-pnpm

Known Issues

Hook health check uses hardcoded port calc 37700 + $(id -u) % 100, but service default is 37777.

Fix: Set port in ~/.claude-mem/settings.json:

{
  "CLAUDE_MEM_WORKER_PORT": "37701"
}

Then restart: pkill -f worker-service