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

harness-sync

v1.2.0

Published

harness-sync is a CLI that syncs AI coding harness skills from a private GitHub catalog into your current project. Supported harnesses: OpenCode, Claude Code, and Codex CLI.

Readme

harness-sync

harness-sync is a CLI that syncs AI coding harness skills from a private GitHub catalog into your current project. Supported harnesses: OpenCode, Claude Code, and Codex CLI.

Prerequisites

  • GitHub CLI (gh) installed and authenticated.
  • Access to the catalog repo you want to use.

Installation

Install the CLI globally using your preferred package manager:

npm i -g harness-sync
pnpm add -g harness-sync
bun add -g harness-sync

Verify the install:

harness-sync -h

Quick Start

  1. Configure your catalog repo.
  2. List skills to see what is available.
  3. Apply skills to your project.
harness-sync init
harness-sync list
harness-sync apply

Commands

harness-sync init

Prompts for the catalog repo in owner/repo format and stores it locally.

harness-sync init

harness-sync list

Lists skills in the catalog with applied status for the current project.

harness-sync list

harness-sync apply

Interactive flow to select harnesses and skills, then apply them.

harness-sync apply

harness-sync

Alias for the interactive apply flow.

harness-sync

harness-sync --version

Prints the CLI version.

harness-sync --version

harness-sync --help

Prints usage help.

harness-sync --help

Non-Interactive Apply

Flags are supported only for harness-sync apply.

harness-sync apply --skills alpha,beta --harnesses opencode,claude,codex --yes

Flags

  • --skills <id1,id2>: Comma-separated skill IDs.
  • --harnesses <opencode,claude,codex>: Comma-separated harness targets.
  • --yes or -y: Auto-confirm overwrites. Requires both --skills and --harnesses.

Catalog Structure

The catalog repo must contain a skills/ directory. Each skill is a folder with a SKILL.md file containing YAML frontmatter:

---
name: Alpha
description: Short description of the skill
---

Example layout:

catalog-repo/
  skills/
    alpha/
      SKILL.md
      ...other files

Where Skills Are Applied

Skills are copied into the current project root.

  • OpenCode: .opencode/skills/<skill-id>
  • Claude Code: .claude/skills/<skill-id>
  • Codex CLI: .codex/skills/<skill-id>

If a destination already exists, the CLI prompts before overwriting unless --yes is used.

Configuration File

The catalog repo setting is stored in:

~/.config/harness-sync/config.json

If XDG_CONFIG_HOME is set, the path becomes:

$XDG_CONFIG_HOME/harness-sync/config.json

Notes

  • The catalog is fetched via gh using a shallow clone.
  • The tool attempts to clone main first, then falls back to master.
  • Temporary catalog clones are cleaned up automatically.