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

@d7x7/pi-good-communication

v0.1.0

Published

good communication discipline for pi — keep conversations oral, complex ideas written

Readme

pi-good-communication

good communication discipline for the pi coding agent.

conversation stays oral and immediate. complex ideas persist as written artefacts.

concept

a pi session is a Shannon communication channel.

  • Information Source (SRC) — the user. encodes intent as natural language.
  • Destination (DST) — the agent. decodes language, acts, encodes response.

each signal should be short, single-purpose, and free of structural noise. this extension enforces that at both ends.

inspired by the WAL GUIDANCE block:

(* One line. One step.
   One step. One job only.
   For LLM steps. Keep text short.
   If more detail is needed, write a document.
   For shell steps. Do not use pipe, && or ||.
   Write a script file instead. *)

oral and written

conversation is oral — immediate, transient, lived. documents and scripts are written — durable, revisable, shared.

complexity routes away from the channel toward four targets:

  • docs/ — project documents. design notes, rationale, decisions.
  • scripts/ — project scripts. reusable, versioned, auditable.
  • tmp/docs/ — transient documents. external dependency notes, scratch reasoning.
  • tmp/scripts/ — transient scripts. one-off helpers, experimental tooling.

the first two are project assets under version control. the last two reference external concerns or material not yet ready to commit.

src-msg

user prompt length guard. two zones based on character count.

  • [0, 160) — pass silently.
  • [160, +infinity) — block.
declare function isBlocked(length: number): boolean;
declare const MAX_CHARS: 160;

src-cmd

user shell command guard. intercepts ! and !! via the user_bash event.

  • [0, 160) — pass.
  • [160, +infinity) — block.
declare function blockResult(msg: string): BlockResult;

dst-bash

agent shell execution guard. two zones based on character count.

  • [0, 160) — pass silently.
  • [160, +infinity) — block.

on bash failure, appends a light suggestion to extract the command into a standalone script for debugging and re-runs.

declare function isBlocked(length: number): boolean;

together

SRC-msg  →  keep prompts short
SRC-cmd  →  keep user shell short
DST-bash →  keep agent shell short

two zones, mechanically enforced. no prompts, no confirmations. no runtime overhead for passes.

this is a communication discipline, not a security boundary. when used with pi-wal, Guard enforces clean structure and WAL records clean steps.