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

@humanlayer/autotune

v0.0.4

Published

Claude SDK PoC

Readme

Claude SDK POC

Multi-agent research orchestrator using the Claude Agent SDK. Spawns parallel specialized agents to gather codebase context for implementation planning.

Usage

# New interactive session
bun run dev                          # Interactive prompt
bun run dev "your research query"    # With initial query
bun run dev --cwd /path/to/repo      # Custom working directory

# Continue/Resume sessions
bun run dev --continue               # Continue most recent session
bun run dev --resume SESSION_ID      # Resume specific session by ID
bun run dev:continue                 # Shortcut for --continue

# Headless/piped mode (runs query and exits)
echo "your query" | bun run dev      # Pipe input
cat query.txt | bun run dev          # From file

Interactive Session

After the initial query, the session stays open for follow-ups:

<session_id> > your follow-up question here

Exiting

  • Type EXIT and press Enter
  • Press Ctrl+C
  • Press Ctrl+D

Session Continuation

  • Session IDs are displayed when a session starts
  • Use --resume SESSION_ID to resume any previous session
  • Use --continue to resume the most recent session
  • Both continuation modes fork the session (original is preserved)

Headless Mode

When stdin is not a TTY (piped input), the tool runs in headless mode:

  • Runs the query and prints the result to stdout
  • Prints session ID to stderr (for scripting/resume)
  • Exits after the first response (no interactive prompt)

Structure

  • index.ts - CLI entry point (Commander.js)
  • src/interactive.ts - Interactive session handler
  • src/research.ts - Research orchestrator (legacy one-shot mode)
  • src/agents/ - 4 specialized research agents

Key Files

| File | Purpose | |------|---------| | src/interactive.ts | Interactive session with AsyncIterable prompt | | src/research.ts | Legacy planning1Research() function | | src/agents/index.ts | Agent exports | | src/evals/run-evals.ts | Eval runner with WorkflowFn type |

If Working On...

Interactive mode: See src/interactive.ts. Uses SDK's AsyncIterable prompt mode for multi-turn conversations.

Evals: See src/evals/. Run bun run eval, accept with bun run eval:accept, diff with bun run eval:diff.

New workflow function: Export from src/research.ts matching (input: ResearchInput) => Promise<ResearchResult>, then add eval cases in run-evals.ts.

Agents: See src/agents/. Each agent is an AgentDefinition with description, tools, model, prompt.

References