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

@cmdctrl/mock-daemon

v0.1.5

Published

CmdCtrl mock daemon for testing - simulates AI agent behavior without real API calls

Readme

Mock Daemon

A mock daemon for E2E testing that simulates AI agent behavior without making real API calls.

Use Cases

  • E2E testing of the full message flow
  • UI development without API costs
  • Demo/showcase scenarios

Installation

cd daemons/mock
npm install
npm run build

Registration

Register with a CmdCtrl server before starting:

cmdctrl-mock register -s http://localhost:4000
cmdctrl-mock register -s https://your-server.ngrok-free.dev

Running

cmdctrl-mock start      # Start daemon
cmdctrl-mock status     # Check status
cmdctrl-mock stop       # Stop daemon

Behavior

By default, the mock daemon:

  • Echoes back user prompts prefixed with **MOCK:**
  • Generates realistic verbose output and progress events
  • Creates JSONL session files in ~/.cmdctrl-mock/sessions/

Message Commands

Control daemon behavior dynamically by prefixing messages with commands:

| Command | Effect | |---------|--------| | /sleep <ms> or /delay <ms> | Wait specified milliseconds before responding | | /tools or /progress | Show 5-8 progress events (Reading, Searching, etc.) | | /error | Simulate an error response | | /ask or /question | Trigger WAIT_FOR_USER with a question |

Examples

| Message | Result | |---------|--------| | Hello world | Normal echo: "MOCK: Hello world" | | /sleep 3000 Hello world | 3 second delay, then echo | | /tools Fix the bug | Shows progress events, then echo | | /error Something broke | Returns ERROR event with message | | /ask Which file? | Returns WAIT_FOR_USER with question options |

Commands are parsed left-to-right, so you can combine them:

/sleep 2000 /tools Do something

This waits 2 seconds, shows progress events, then echoes "Do something".

CLI Options

Customize default behavior via command line:

cmdctrl-mock start --delay-min 500 --delay-max 2000  # Custom response timing
cmdctrl-mock start --ask-probability 0.5             # 50% chance of asking questions
cmdctrl-mock start --error-rate 0.3                  # 30% chance of errors

Configuration

Config files are stored in ~/.cmdctrl-mock/:

  • config.json - Server URL, device ID, device name
  • credentials - Authentication tokens (chmod 600)
  • sessions/ - JSONL session files

Development

Run directly without building:

npm run dev -- start
npm run dev -- status