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

workharness

v0.1.8

Published

Install and manage WorkHarness workflows in AI coding projects.

Readme

WorkHarness

WorkHarness is a workflow harness that helps AI coding agents handle large tasks in stages.

The workflow is:

clarify -> context-gather -> plan -> generate -> evaluate

Each run's state and artifacts are stored under .workharness/runs/<run-id>/, and automatic workflows can continue through Codex or Claude Stop hooks.

Supported Agents

  • Claude Code
  • Codex CLI

When using Codex CLI, Codex may ask you to approve project hook execution. To keep WorkHarness workflows moving correctly, make sure to approve the Stop hook in Codex. If you do not approve it, the workflow will not continue after certain stages. For details, see the official Codex hooks documentation.

Install

Run WorkHarness from the directory where you want to install it.

npm create workharness@latest
pnpm create workharness@latest
yarn create workharness@latest

The installer checks that the current directory is inside a git repository and that python3 is available. In a monorepo, run the create command from the package or app directory that WorkHarness should manage. It then asks which agent integrations to enable.

[x] Codex
[ ] Claude

To install without prompts:

npm create workharness@latest -- --agents codex,claude
pnpm create workharness@latest --agents codex,claude
yarn create workharness@latest --agents codex,claude

Agent Integrations

Agent selections are stored in:

.workharness/install.json

The selected agents create the required hooks and skill directories.

  • Codex: .codex/config.toml, .codex/hooks.json, .codex/skills
  • Claude: .claude/settings.json, .claude/skills

.workharness/skills is the source of truth. Codex/Claude skill directories are generated output copied from this source. Symlinks are not used. After editing .workharness/skills, run sync explicitly to reflect those changes in Codex/Claude skills.

Commands

| Purpose | npm | pnpm | Description | | --- | --- | --- | --- | | Add Agent | npm run workharness:add-agent | pnpm run workharness:add-agent | Choose supported agents from a checkbox prompt. | | Add Agent Directly | npm exec workharness -- add agent claude | pnpm exec workharness add agent claude | Add a specific agent directly. Currently supports codex and claude. | | Sync Skills | npm run workharness:sync | pnpm run workharness:sync | Reflect .workharness/skills source into Codex/Claude generated skills. | | Check Status | npm run workharness:doctor | pnpm run workharness:doctor | Check install state and agent skill targets. | | Dashboard | npm run workharness:dashboard | pnpm run workharness:dashboard | Open the dashboard on the default port 4673. | | Dashboard With Port | npm exec workharness -- dashboard -p 6006 | pnpm exec workharness dashboard -p 6006 | Open the dashboard on a specific port. | | Update | npx workharness@latest upgrade | pnpm dlx workharness@latest upgrade | Update .workharness to the latest package payload. |

Before replacing .workharness/skills, upgrade backs up the current skill source to .workharness/backups/skills-<timestamp>/. WorkHarness-managed files that no longer exist in the new package payload are removed.

sync does not download or replace the core .workharness payload. It overwrites enabled agent hooks and generated skill copies from the installed .workharness/skills source.

For yarn projects, run the same script names with yarn.

yarn workharness:add-agent
yarn workharness:dashboard
yarn workharness:sync
yarn workharness:doctor

Quick Start

Ask the agent:

Use `workharness` to implement <task>.

Before starting, choose:

  • loop count: maximum number of generate -> evaluate retries when evaluate fails
  • commit mode: none, phase, final

Defaults:

loop count: 2
commit mode: none

Dashboard

By default, the dashboard first tries http://127.0.0.1:4673/ and falls back to an available port if 4673 is busy.

The dashboard shows the current active run, stage progress, artifacts, diagnostics, and run history.

Project Guidance

If your project has architecture docs, coding rules, or review criteria, copy the example context file:

cp .workharness/context.example.json .workharness/context.json

Then edit .workharness/context.json.

  • context-gather.documents: documents to reference before planning
  • context-gather.skills: agent skills to consult for task-relevant conventions
  • evaluate.documents: documents to reference during review
  • evaluate.skills: agent skills to consult as review criteria
  • evaluate.rules: additional review rules