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

@blueagent/builder

v0.1.15

Published

CLI for Blue Agent — blue idea / build / audit / ship / raise / new / init / doctor / chat / validate

Downloads

1,973

Readme

@blueagent/builder

CLI for Blue Agent — the AI-native founder console for Base builders.

Install

npm install -g @blueagent/builder
blue init   # installs skill files for grounding

Commands

Workflow

blue idea "a USDC streaming payroll app on Base"
blue build "USDC streaming payroll: ERC-20 + x402 payment"
blue audit "review my streaming contract for reentrancy"
blue ship  "checklist for mainnet launch of payroll app"
blue raise "pitch for a USDC payroll agent on Base"

You can also pipe input:

cat BRIEF.md | blue build
cat contracts/Token.sol | blue audit

Scaffold

blue new my-agent --template base-agent   # Bankr agent with wallet + x402
blue new my-api   --template base-x402    # paid API service
blue new my-token --template base-token   # ERC-20 + Uniswap v4 hook

Setup

blue init   # copies skills/*.md to ~/.blue-agent/skills/

Options

All workflow commands accept:

  • --model <model> — Bankr LLM model (default: claude-sonnet-4-6)
  • --max-tokens <n> — max response tokens

Environment

BANKR_API_KEY=your_key   # required — get at bankr.bot
BLUE_AGENT_SKILLS_DIR=/custom/skills/path  # optional override

How grounding works

Each command loads skill files relevant to the task before calling Bankr LLM:

| Command | Skills loaded | |---|---| | idea | base-standards, base-addresses, blue-agent-identity | | build | base-standards, base-addresses, bankr-tools | | audit | base-standards, base-addresses, base-security | | ship | base-standards, bankr-tools | | raise | blue-agent-identity |

Skills are loaded from (first found wins):

  1. BLUE_AGENT_SKILLS_DIR env var
  2. ~/.blue-agent/skills/ (installed via blue init)
  3. Monorepo skills/ directory (dev)

Built by

Blocky Studio@blocky_agent