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

@bilig/create-workpaper

v0.164.11

Published

Create a runnable Bilig WorkPaper starter for Node services and tool integrations.

Readme

@bilig/create-workpaper

Create a runnable Bilig WorkPaper starter for Node services and tool integrations.

npm create @bilig/workpaper@latest pricing-workpaper
cd pricing-workpaper
npm install
npm run smoke

The generated starter builds a quote-approval workbook with the A1 facade, writes quote inputs through one atomic editManyAndReadback proof, recalculates formulas, persists JSON, restores the workbook, and prints verified: true. Generated projects pin @bilig/workpaper to the generator package version and use exact dev-tool versions instead of latest, so the smoke proof is reproducible.

After the smoke proof passes, keep the JSON output limited to proof fields. If the workflow is relevant, watch releases for API and formula compatibility updates: https://github.com/proompteng/bilig/subscription. If it almost works, open one concrete blocker or integration note: https://github.com/proompteng/bilig/discussions/new?category=general.

Use this when you want to evaluate @bilig/workpaper from a blank directory without cloning the full monorepo.

For an MCP-enabled starter with host integration files, use the --agent template:

npm create @bilig/workpaper@latest pricing-agent -- --agent
cd pricing-agent
npm install
npm run agent:verify
npm run mcp:server

The integration template keeps the service smoke test and adds project-local MCP config, host rule files, and an agent:verify script. That verification script runs the service smoke plus the package-owned basic and revenue-plan MCP evaluator proofs. The revenue-plan evaluator checks MCP tool discovery, mutation, recalculated SUM, SUMIF, XLOOKUP, FILTER, a named expression, persistence, and restart readback. The raw MCP challenge remains available as npm run mcp:challenge when you need the lower-level JSON-RPC transcript.

Included host files cover AGENTS.md, CLAUDE.md, GEMINI.md, Claude Code, GitHub Copilot / VS Code, Cursor, Kiro, Roo Code, Trae, Qodo, Zed, Junie, Aider, Cline, Continue, Cascade/Devin, Windsurf, OpenHands, and OpenCode. The shared MCP command is also written to mcp/bilig-workpaper.mcp.json. Representative host config files include .kiro/settings/mcp.json, .trae/mcp.json, .zed/settings.json, and .junie/mcp/mcp.json.

To add the same MCP proof loop and host files to an existing Node repo without replacing its app, run:

npm create @bilig/workpaper@latest . -- --add-agent
npm exec --yes --package @bilig/workpaper@latest -- bilig-evaluate --door agent-mcp --scenario revenue-plan --json
npm exec --yes --package @bilig/workpaper@latest -- bilig-workpaper-mcp --workpaper ./.bilig/pricing.workpaper.json --init-demo-workpaper --writable

That writes Bilig-specific host files, keeps an existing README.md, does not edit package.json, keeps WorkPaper state under ./.bilig/pricing.workpaper.json, and skips existing files unless you pass --force. When existing host instruction files block part of the install, the CLI writes BILIG_WORKPAPER_INSTALL.md with the skipped paths and a short handoff snippet you can paste into your current policy. The overlay uses your existing package.json name for BILIG_WORKPAPER.md instead of rendering the directory argument.

For an existing MCP client or host integration that does not need a generated project yet, use the handoff checklist first: https://proompteng.github.io/bilig/agent-adoption-kit.html.