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

@cobuild/cli

v0.1.5

Published

TypeScript CLI + agent skill for running wallet actions through the interface app's API (`/api/buildbot/*` routes).

Readme

cli

TypeScript CLI + agent skill for running wallet actions through the interface app's API (/api/buildbot/* routes).

Warning This project drives real wallet operations. Use test networks and small amounts while validating your setup.

What You Get

  • cli CLI for setup, wallet, send, and tx
  • cli docs command for Cobuild documentation search via API
  • Installable agent skill package at skills/cli
  • JSON-first command output for automation

Requirements

  • Node.js 20+
  • pnpm
  • Running interface app URL (for example http://localhost:3000)

Install CLI

From this repo:

pnpm install
pnpm build

Run locally from the repo:

pnpm start -- --help

Run from npm (published package):

npx @cobuild/cli --help

Quick Start (CLI)

# 1) Configure and bootstrap wallet access
pnpm start -- setup --url http://localhost:3000 --network base-sepolia --agent default
# or: pnpm start -- setup --dev --network base-sepolia --agent default

# 2) Verify config (token is masked)
pnpm start -- config show

# 3) Check wallet
pnpm start -- wallet --network base-sepolia --agent default

If cli is on your PATH, you can drop pnpm start -- and run cli <command> directly.

Agent Skill Setup

This is the fastest path for people who want to use the agent skill.

Option A: Install from local checkout

mkdir -p "${CODEX_HOME:-$HOME/.codex}/skills"
cp -R skills/cli "${CODEX_HOME:-$HOME/.codex}/skills/cli"

Option B: Install from GitHub

install-skill-from-github.py --repo <owner>/<repo> --path skills/cli

Verify + use

  1. Restart Codex after installing the skill.
  2. Confirm the skill folder exists at ${CODEX_HOME:-$HOME/.codex}/skills/cli.
  3. Invoke with prompts like: Use $cli to run wallet on base-sepolia.

Setup Details

setup supports secure browser approval and non-interactive token sources. It defaults to:

  • interface URL: https://co.build (or http://localhost:3000 with --dev)
cli setup [--url <interface-url>] [--dev] [--token <pat>|--token-file <path>|--token-stdin] [--agent <key>] [--network <network>] [--json] [--link]
  • Browser approval flow:
    • Opens /home in your interface app and waits for one-time localhost callback approval.
    • Falls back to hidden manual token prompt only if approval fails or times out.
  • Machine output:
    • Use --json or COBUILD_CLI_OUTPUT=json.
  • Global command install:
    • Use --link during setup to run pnpm link --global automatically when possible.

Config Resolution Order

For setup, values resolve in this order:

  1. Interface URL: --url -> saved config URL -> COBUILD_CLI_URL -> default (https://co.build, or http://localhost:3000 with --dev).
  2. Network: --network -> COBUILD_CLI_NETWORK -> base-sepolia.
  3. Token: exactly one of --token/--token-file/--token-stdin -> saved config token -> interactive browser approval/manual prompt.

For runtime commands:

  • Agent key: --agent -> saved config agent -> default.
  • Exec network (send/tx): --network -> COBUILD_CLI_NETWORK -> base-sepolia.

Output Contract

  • wallet, docs, tools, send, and tx emit JSON on success.
  • setup emits JSON in non-interactive mode or when --json is set.
  • Failures exit non-zero and print human-readable diagnostics.

Command Auth Requirements

  • No pre-existing token needed: setup, config set, config show, and --help.
  • Requires saved config token + interface URL: wallet, docs, tools, send, tx.
  • Usually requires funded wallet: send, and most state-changing tx calls.

Command Reference

cli wallet [--network <network>] [--agent <key>]
cli docs <query> [--limit <n>]
cli send <token> <amount> <to> [--network <network>] [--decimals <n>] [--agent <key>] [--idempotency-key <uuid-v4>]
cli tx --to <address> --data <hex> [--value <eth>] [--network <network>] [--agent <key>] [--idempotency-key <uuid-v4>]

Examples:

cli wallet --network base-sepolia --agent default
cli docs setup approval flow --limit 5
cli docs -- --token-stdin
cli send usdc 0.10 0x000000000000000000000000000000000000dEaD --network base-sepolia --agent default
cli tx --to 0x000000000000000000000000000000000000dEaD --data 0x --value 0 --network base-sepolia --agent default

If your query starts with a dash (for example, --token-stdin), insert -- before the query so the CLI treats it as text, not flags.

send and tx always include both X-Idempotency-Key and Idempotency-Key headers.

Troubleshooting

  • cli: command not found
    • Run via pnpm start -- <command> from this repo, or run setup with --link.
  • Setup succeeds but wallet bootstrap fails
    • Check interface logs, apply CLI SQL migrations, and verify CDP_API_KEY_ID, CDP_API_KEY_SECRET, and CDP_WALLET_SECRET.
  • Wrong URL/network
    • Re-run setup with explicit --url and --network.

Developer Commands

pnpm build
pnpm typecheck
pnpm test
pnpm test:coverage
pnpm verify  # typecheck + coverage-inclusive test run
pnpm docs:drift
pnpm docs:gardening
pnpm review:gpt

Release Flow (npm)

Run release checks first:

pnpm run release:check

Create and push a release tag (which triggers .github/workflows/release.yml to publish):

pnpm release:patch   # or: pnpm release:minor / pnpm release:major

For pre-releases:

bash scripts/release.sh preminor --preid alpha
# or: bash scripts/release.sh preminor --preid beta

For exact version and dry-run:

bash scripts/release.sh 1.2.3-rc.1 --dry-run

What the release script does:

  • requires a clean git worktree
  • requires the current branch to be main (override only with --allow-non-main)
  • requires origin remote, package name @cobuild/cli, and package.json.repository.url = https://github.com/cobuildwithus/cli
  • runs pnpm verify (typecheck + coverage-inclusive test run), pnpm docs:drift, pnpm docs:gardening, pnpm build, and npm pack --dry-run
  • bumps version with npm version --no-git-tag-version
  • updates CHANGELOG.md
  • generates Codex-style release notes at release-notes/v<version>.md
  • creates release commit + v* tag
  • validates tag/version match
  • pushes commit + tags so GitHub Actions can publish to npm

CI release workflow (.github/workflows/release.yml) does:

  • tag/version validation against package.json including package identity + canonical repository metadata
  • docs drift + doc gardening gates before packaging
  • tarball build as an artifact before publish
  • GitHub Release creation from release-notes/v<version>.md (fallback: generated on CI)
  • npm Trusted Publishing via OIDC with prerelease dist-tag routing and idempotent publish handling

Changelog + release notes helpers:

pnpm run changelog:update -- 0.2.0
pnpm run release:notes -- 0.2.0 /tmp/release-notes.md

Architecture + Process Docs

  • AGENTS.md: routing rules and mandatory workflow
  • ARCHITECTURE.md: system-level design
  • agent-docs/index.md: canonical docs map