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

pi-craft

v0.1.18

Published

An opinionated Pi workflow suite for planning, intent clarification, permissions, subagents, Git automation, project initialization, and publishing.

Readme

PiCraft

An opinionated workflow suite for the Pi coding agent.

The published npm package is pi-craft.

Install

pi install npm:pi-craft

If Pi still lists the historical npm:@losomz/picraft identity, remove it before installing npm:pi-craft; Pi treats the two npm names as different packages.

Restart Pi after installation, or run /reload in an existing Pi session.

Included Workflows

  • Plan: a persistent planning mode with a fixed plan/normal status line that distinguishes inquiries from implementation tasks, gates execution on a proposed plan, and guards write tools with explicit execution handoff. Use /plan menu to reopen dismissed execution choices while the current plan is available.
  • Questionnaire: structured intent clarification with single-choice, multiple-choice, and free-form answers in the Pi TUI.
  • Permission: project-boundary and sensitive-file approval with parent/child session authorization sharing, session-scoped Ask or Allow all modes, a persistent perm status line, /permissions list overlay details, and external-access audit records.
  • Throughput: live and final AI output throughput with provider usage, delta fallback estimation, TTFT, and /throughput details.
  • Subagent: bundled General, Explore, and Scout agents with per-agent model and thinking configuration. Scout uses a controlled Git tool and deterministic checkouts under ~/.cache/picraft/scout/repos.
  • Git: commit, pull, and branch workflows under /git.
  • Init: repository-aware AGENTS.md initialization with reusable project templates.
  • Blog: file-based product, technical, release, and work log workflows.

PiCraft requires Pi 0.80.4 or newer. MCP support is provided by Pi itself starting with Pi 0.99.0.

Plan Analysis Tools

Plan keeps a conservative built-in tool set. Add trusted read-only extension tools in ~/.pi/agent/picraft.json, or in a trusted project's .pi/picraft.json:

{
  "plan": {
    "tools": ["codegraph_explore", "codegraph_search", "memory_search"]
  }
}

Configured tools must already be registered and active. Do not list custom tools that can modify files or external state.

Pi Native MCP

PiCraft no longer bundles an MCP client or /mcp extension. Pi 0.99.0 and newer versions provide MCP over stdio and Streamable HTTP, including OAuth, resources, and tool exposure controls.

Configure global servers in ~/.pi/agent/mcp.json or project servers in <project>/.pi/mcp.json. Use pi mcp add, pi mcp list, or /mcp to manage them. Existing PiCraft configurations in <project>/.mcp.json must be moved to .pi/mcp.json.

Update

pi update npm:pi-craft

Pinned installs such as npm:[email protected] do not update automatically. Install a newer explicit version to move a pinned package.

Uninstall

pi remove npm:pi-craft

Try From Source

From an AgentFramework checkout:

pi --no-extensions --no-skills --no-prompt-templates --no-themes -e ./packages/picraft

Do not enable npm, Git, project-local, or manually copied versions of the same PiCraft extensions at the same time. Duplicate sources register the same tools, commands, shortcuts, and event handlers.

Security

Pi extensions execute with the current user's system access. Review the source before installation. PiCraft Permission is a tool-call approval layer, not an operating-system sandbox; headless approval failures default to rejection. For external reads, an always grant uses a detected project, package, or engine manifest root so files in the same dependency tree do not prompt individually; external write grants remain limited to the direct parent directory. Existing regular files dragged or pasted into the Pi TUI receive exact, session-scoped read approval, including sensitive files the user explicitly supplies; parent directories, sibling files, and write operations remain restricted. PiCraft's exact Scout cache root is trusted for ordinary reads by all agents, while sensitive-file checks and write approval remain active. Only the bundled Scout receives the managed repository tool.

Credentials, model configuration, sessions, logs, and other machine-local Pi state are not distributed by this package.

Source and issue tracking: Losomz/AgentFramework