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

@pirog/me

v1.0.0

Published

pirog, codified: dotfiles, skills, Codex plugins, workflows, and automations.

Readme

me

me gives a Mac pirog's tools, dotfiles, habits, and prejudices—and gives Codex a job beyond producing agreeable paragraphs. workstation setup and GitHub-backed task work, in one editable profile.

use it as:

  • an operator profile to set up a computer for manual use as pirog.
  • a Codex binding to have Codex work with pirog's guidance and preferences, automate assigned GitHub issue work, and review pull requests on request.

we recommend using both.

requires macOS 26 or newer. see Inventory for what ships and Piroboot for bootstrap options.

quickstart

for workstation and Codex setup, provide a 1Password service account token and run the hosted bootstrap. it installs applications and dotfiles and retrieves the configured private SSH keys:

/bin/bash -c "$(curl -fsSL https://boot.pirog.me/boot.sh)" piroboot \
  --op-token "$OP_TOKEN" \
  --tanaab canon:codex-plugin \
  --tanaab openclaw-agent-system:codex-plugin-build

for workstation-only setup, omit the two --tanaab selections. see Piroboot for the full option reference.

for the skills alone, install piroplugin without running the machine bootstrap:

npx --yes --package=@tanaab/codex-tools@1 -- codex-tools install npm:@pirog/me@latest --marketplace pirostore

piro-skill-author also requires the Canon (tanaab) plugin for shared authoring and validation.

after pirobooting

operator profile

  • 1Password: sign in, unlock, and enable Developer > Integrate with 1Password CLI and Show 1Password Developer experience. keep the beta CLI for 1Password Environments; check access with op vault list.
  • Tailscale: if using the desktop app, sign in and join tanaab.dev. leave formula-backed services in place; tailscale status --json should report the local node running and online.

Codex binding

the quickstart's two --tanaab options install Agent System (agent-system) and Canon (tanaab). sign into Codex, install piroplugin from Pirostore, and confirm all three plugins are enabled.

connect GitHub as pirog and monday.com as Michael Pirog. authorize Agent System's hook through /hooks, start a fresh chat, and paste:

Use $agent-system-codex-binding to bind this plugin to /Users/pirog/tanaab/me.

confirm the workspace containing .agent-system/agent.yaml. after binding, start a fresh chat and paste:

Use $agent-system-doctor to check this workspace. Then use $agent-system-install
for any declared setup repairs and to reconcile its automations.
Run $agent-system-doctor again and report anything still unresolved.

usage

direct invocation

paste the prompt you need into Codex, replacing the placeholder:

# start or resume an issue without assigning it or enabling scheduled intake
use $agent-system-task-launch to work on <issue URL>.

# review an existing PR through the temporary native startup route
start a review of <PR URL> using references/codex-task-access.md in the bound Me workspace.

# retire managed work without closing the GitHub issue
use $agent-system-task-retirement to clean up <issue URL>.

# check workspace readiness without applying repairs
use $agent-system-doctor to check this workspace.

# rewrite supplied prose in the shared voice
use $piro-voice to rewrite the following text: <text>.

see the full cheat sheet for maintenance and other prompts. existing-PR startup and unmanaged chat cleanup follow the temporary native guidance.

issue assignments

for automatic pickup, set up assignment intake once, then assign work through GitHub:

  1. configure approved assigners, repository owners, and the workflow mode in the profile. see Agent System's GitHub workflow configuration.
  2. use $agent-system-install to activate and reconcile intake, then $agent-system-doctor to check saved state. see the Codex automation contract for how scheduled jobs are managed.
  3. have an approved assigner assign an eligible issue to @pirog. include a clear outcome, acceptance criteria, and a reproduction for bugs. follow progress in its Codex chat and review any resulting PR.

Doctor checks saved state; a successful scheduled run is separate evidence.

development

use the runtimes in .node-version and .bun-version:

# prepare the checkout
git clone [email protected]:pirog/me.git
cd me
bun install --frozen-lockfile --ignore-scripts

# run tests, lint, formatting, and ShellCheck
bun run test
bun run lint

edit the source configuration, not generated files. bun run build and Leia scenarios are CI-owned by default: they generate dist/ or mutate macOS runner state. read the example guidance before changing executable examples.

support and releases

bring bugs, regressions, and feature requests to the GitHub issue queue. see CHANGELOG.md and GitHub releases for changes. piroplugin releases ship through npm; see plugin sources.

maintainers

contributors

made with contrib.rocks.