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

@ogulcancelik/pi-goal

v0.1.1

Published

Autonomous goal pursuit for pi. Break work into tasks, spawn worker agents, track progress via files on disk.

Readme

pi-goal

Autonomous goal pursuit with sub-agent workers for pi. Break work into tasks, spawn isolated workers, track progress via files on disk.

Install

pi install npm:@ogulcancelik/pi-goal

Or add manually to ~/.pi/agent/settings.json:

{
  "packages": ["npm:@ogulcancelik/pi-goal"]
}

What it does

Turns multi-step work into structured goals with task breakdowns. You discuss a goal with the agent, it creates task documents with specific file paths and acceptance criteria, then spawns fresh worker agents to implement each task independently. Progress lives on disk — survives compaction, restarts, and context loss.

How it works

  1. You and the agent discuss a goal
  2. Agent creates structured tasks with goal add_task — rich markdown docs with file paths, constraints, and acceptance criteria
  3. Agent runs workers with goal run — each gets a fresh pi subprocess, reads only its task doc, implements immediately
  4. Results and learnings accumulate on disk in the goal directory
  5. Agent stays grounded via system prompt injection — active goal state is re-injected every turn, even after compaction

File structure

.pi/goals/
├── ACTIVE                          # slug of active goal
└── <goal-slug>/
    ├── GOAL.md                     # goal description
    ├── STATE.json                  # machine-readable state (tasks, status)
    ├── LEARNINGS.md                # cross-task knowledge (auto-appended by workers)
    ├── tasks/
    │   ├── 01-<task-name>.md       # task spec (what workers read)
    │   └── 02-<task-name>.md
    ├── results/
    │   ├── 01.md                   # worker output
    │   └── 02.md
    └── sessions/                   # worker session logs (for observability)

Actions

| Action | Description | |------------|--------------------------------------------------------------------------| | create | Create a new goal with name, description, optional workerModel | | add_task | Add a task with a name and full markdown spec | | run | Execute all pending tasks sequentially with isolated worker agents | | status | Check current goal progress, task states, and learnings |

Worker behavior

  • Fresh pi subprocess per task — no shared context between workers
  • Tools available: read, edit, write, grep, find, ls (no bash)
  • Workers read their task doc first, then implement immediately
  • Learnings from each worker are auto-extracted and appended to LEARNINGS.md
  • Worker sessions are saved in the goal directory for observability

Configuration

Pass workerModel when creating a goal to control which model runs workers. Defaults to the facilitator's current model.

goal create —  name: "my goal", workerModel: "anthropic/claude-sonnet-4-20250514"

This is v0.1 — more configuration options coming.

Requirements

License

MIT