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

custom-workflow-installer

v0.6.0

Published

Custom workflow system installer for Claude Code

Readme

Custom Workflow System

A sophisticated issue workflow system for Claude Code that provides structured issue management, mode-based interaction control, and customizable bash command permissions.

Features

  • Issue Management: Create and orchestrate issues with structured templates
  • Mode Controller: Discussion/Implementation mode switching for safer interactions
  • Configurable Commands: Allow specific bash commands in discussion mode
  • Clean Updates: Preserves user customizations during updates
  • Hook System: PreToolUse hooks for controlling tool access

Installation

Via NPM (Recommended)

npx custom-workflow-installer

Local Development

./scripts/install-local.sh [target_directory]

System Architecture

Directory Structure

  • .claude/ - Claude Code configuration (commands, hooks, settings)
  • .issues/ - Workflow data (templates, state, config, docs)

Mode Controller

The workflow enforces two operational modes:

Discussion Mode (default):

  • Read-only operations allowed
  • Markdown editing allowed
  • Configurable safe bash commands
  • Type "proceed" to switch to implementation mode

Implementation Mode:

  • All operations allowed
  • Returns to discussion mode on task completion

Configuring Allowed Bash Commands

Edit .issues/config/workflow-config.json to customize allowed commands:

{
  "modeController": {
    "allowedBashCommands": {
      "exactMatches": ["pwd", "ls", "whoami"],
      "prefixMatches": ["git status", "npm list"],
      "regexPatterns": ["^echo [^;&|`$()<>]+$"]
    }
  }
}

Default Safe Commands

  • Navigation: pwd, ls, tree
  • File viewing: cat, head, tail
  • Searching: grep, find, rg
  • Git queries: git status, git diff, git log
  • Package info: npm list, npm view
  • System info: which, node --version

Available Commands

  • /create-issue - Create new issues with structured templates
  • /orchestrate-issue - Orchestrate workflow for existing issues

Development

Repository Structure

custom-workflow/
├── templates/           # Files for NPM package
│   ├── claude/         # Claude Code config
│   └── issues/         # Workflow data
├── bin/                # NPM installer
├── scripts/            # Development tools
└── package.json        # NPM configuration

Testing Workflow

  1. Make changes to templates
  2. Run ./scripts/install-local.sh workflow_testing
  3. Test in workflow_testing/ directory
  4. Bump version and push to publish

Publishing

The workflow is published automatically when pushing to main with an incremented version number.

License

MIT

Support

Report issues at: https://github.com/secondcircle/custom-workflow/issues