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

modular-chunks-cli

v0.1.3

Published

CLI & MCP server for Modular Chunks — feeds approved chunk contracts to coding agents and validates output against contracts

Readme

Modular Chunks CLI

A command-line tool that bridges the Modular Chunks platform with your local development environment and Claude Code.

Install

cd cli
npm install
npm run build
npm link          # exposes `modular` globally

Workflow

Platform (browser)          CLI                     Claude Code
─────────────────          ─────────────────────   ──────────────────────
1. Build chunks in UI  →   2. modular init
                           3. modular pull      →   4. modular serve  (MCP)
                                                    5. [Claude builds chunk]
                           6. modular validate  →
                           7. modular sync      →   Platform sees PASS/FAIL

Commands

| Command | Description | |---------|-------------| | modular init | Set up .modular/config.json (platform URL, project ID, API token) | | modular pull | Pull approved chunk contracts from the platform into .modular/cache.json | | modular status | Show all chunks with approval and validation status | | modular show <n> | Print full agent prompt for chunk N (or 00 for project context) | | modular next | Print prompt for the next unvalidated approved chunk | | modular validate [chunk] [--dir <path>] | Run structural validation against source files | | modular sync [chunk] | POST validation results back to the platform | | modular serve | Start MCP stdio server for Claude Code |

Claude Code MCP integration

Add to your Claude Code MCP config (e.g. .claude/mcp.json):

{
  "mcpServers": {
    "modular-chunks": {
      "command": "node",
      "args": ["/path/to/cli/dist/index.js", "serve"]
    }
  }
}

Claude Code will then have access to these tools:

  • get_project_context — full project brief + architecture (Chunk 00)
  • list_chunks — all chunks with status
  • get_current_chunk — next chunk to build
  • get_chunk — any specific chunk by number or name
  • mark_chunk_validated — mark pass/fail after manual review

Platform setup

The Sync to CLI button in the Assembly page (Stage 06) must be clicked first. This POSTs the current project state to /api/assembly/contracts. The CLI pull command reads from this endpoint.

The optional CONTRACTS_INBOUND_API_KEY environment variable on the platform enables auth. Set apiToken in .modular/config.json on the CLI side to match.