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

harnessc

v1.0.0-alpha.10

Published

Alpha Harness config CLI for validating, initializing, previewing, and activating AI agent configuration.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

reachjalilreachjalil

Keywords

harnesscharness-configcliai-agentsagent-configurationcodexclaudecursorgeminipromptsskills

Readme

harnessc

Website Specification npm harnessc Security License

Public npm package for the alpha Harness config CLI.

Harness config is a repository-local standard for keeping AI agent prompts, skills, rules, plugins, and root instruction files in one reviewed .harness source tree, then projecting them into explicit runtime folders such as .agents, .claude, .cursor, and .gemini.

Run harnessc from anywhere inside a repository. It searches upward for ./.harness/harness.toml, validates the selected config, explains source or output paths, and prints the next useful command.

Privacy And Telemetry

Harness config does not collect telemetry. The harnessc CLI does not send analytics, usage events, file paths, repository names, command history, machine identifiers, or error reports. Activation, validation, and planning run locally against files in your repository, and the CLI does not make network requests during normal operation.

Quick Start

npx harnessc
npx harnessc init
npx harnessc validate
npx harnessc explain .agents/skills/review/SKILL.md
npx harnessc activate
npx harnessc activate --yes

Common Commands

harnessc
harnessc init
harnessc validate
harnessc explain .agents/skills/review/SKILL.md
harnessc activate
harnessc activate --yes

harnessc explain <path> is read-only introspection. It can explain a projected output such as .agents/skills/review/SKILL.md, a repo-relative dir output such as AGENTS.md, or a configured source path such as .harness/local/resources/skills/review/SKILL.md. With --json, it includes source and target-output .harnessIgnore traces so automation can see the winning rule.

Filesystem Semantics

  • Symlinks are treated as leaf entries and are not followed.
  • Target symlinks that occupy projected paths are conflicts unless replacement is explicitly selected.
  • Managed target files update from the current source projection.
  • Files declared in .harnessMutable are created once, then left to the runtime.
  • Unmanaged target files are preserved unless cleanup is explicit.
  • Target-output .harnessIgnore and .harnessProfile files are protected local controls.
  • Fixed inputs produce deterministic activation plans.

Links

  • Website: https://www.harnessconfig.dev/
  • Specification proposal: https://www.harnessconfig.dev/specifications/v1/
  • GitHub: https://github.com/reachjalil/harness-config
  • Release notes: https://github.com/reachjalil/harness-config/blob/main/docs/RELEASE_NOTES.md
  • Issues: https://github.com/reachjalil/harness-config/issues
  • Security policy: https://github.com/reachjalil/harness-config/security/policy

Packages

  • harnessc: public npm CLI package.
  • @harnessconfig/cli: scoped implementation package used by harnessc.
  • @harnessconfig/core: TypeScript reference implementation for tools.