publish-harness

publish-harness is a skill for Claude Code from ruvnet/metaharness. It costs 37 tokens per session (379 once invoked), scanned A, original, MIT.

A release tool for publishing a generated JavaScript package, called a harness, to npm, the package registry for JavaScript projects. It builds and tests the package, signs and verifies a release record, then prepares or performs the publish step.

In plain words
What is it for?
Use it to run a dry-run package release or publish a tagged package publicly with npm provenance, provided the required signing key and npm credentials are available.
Why use it?
It groups release checks and publishing into one ordered process. This reduces the chance of publishing code that has not passed its tests or whose release record cannot be verified.

Skill for Claude Code

Written for Claude Code: a Claude Code plugin manifest. Also seen: mentions Codex.

Part of the agent-harness-generator plugin — 14 skills, 1 plugin shipped together

Good fit Use it to run a dry-run package release or publish a tagged package publicly with npm provenance, provided the required signing key and npm credentials are available.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ruvnet/metaharness/publish-harness
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ruvnet/metaharness --skill publish-harness
Clone the repo
git clone --depth 1 https://github.com/ruvnet/metaharness

Made for: Claude Code.

Or install agent-harness-generator, the plugin that ships this one along with the rest of its 14 skills, 1 plugin.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for publish-harness

README.md
[![agentmods](https://agentmods.dev/badge/skills/ruvnet/metaharness/publish-harness/github.svg)](https://agentmods.dev/skills/ruvnet/metaharness/publish-harness)
Your own site
<a href="https://agentmods.dev/skills/ruvnet/metaharness/publish-harness"><img src="https://agentmods.dev/badge/skills/ruvnet/metaharness/publish-harness/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for publish-harness

Your own site · 80×15
<a href="https://agentmods.dev/skills/ruvnet/metaharness/publish-harness"><img src="https://agentmods.dev/badge/skills/ruvnet/metaharness/publish-harness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 379 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.00379
Opus 5 $0.00018 $0.00189
Sonnet 5 $0.00007 $0.00076
Haiku 4.5 $0.00004 $0.00038

Measured 10d ago against content hash 4ff514d3ea9c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

publish-harness scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude-plugin/skills/publish-harness/SKILL.md · 47 lines

What it actually says

publish-harness

Codex skill that runs the full smoke-test → witness-sign → npm publish pipeline for a generated harness.

What it does

  1. Builds the harness with npm run build
  2. Runs npm test to confirm green tests
  3. Calls harness sign to produce a fresh witness manifest (requires WITNESS_SIGNING_KEY env)
  4. Confirms harness verify accepts the freshly signed manifest
  5. Either:
    • dry_run=true (default): runs npm publish --dry-run and reports tarball stats
    • dry_run=false: runs the real npm publish --provenance --access public

Usage from Codex

/publish-harness path=./my-harness
/publish-harness path=./my-harness dry_run=false

Equivalent CLI

cd ./my-harness
npm run build
npm test
harness sign
harness verify
npm publish --provenance --access public

Required env

  • WITNESS_SIGNING_KEY — 64-hex-char ed25519 seed (fetch from GCP Secret Manager via harness secrets fetch WITNESS_SIGNING_KEY)
  • NPM_TOKEN — npm registry credential (Codex skill assumes the host has it set, or fetches via harness secrets fetch NPM_TOKEN)

See also

  • validate-harness — release-readiness gate (run this FIRST)
  • harness-secrets — manage GCP-stored signing/publishing tokens
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 47 lines · 37 tokens per session scan A 4ff514d3ea9c

Subscribe to this mod's changes

publish-harness is a skill published in the GitHub repository ruvnet/metaharness (642 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 379 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

github

Full GitHub CLI control — issues, PRs, code reviews, repo management. Uses gh CLI with auth detection, rate limiting, and templates. Triggers on: github, issue, pull request, PR, code review, repo, branch, label, assignee, milestone, release, workflow, actions.

adolfousier/opencrabs · 0 tokens

release-prep

Prepare release documentation including CHANGELOG entry, announcement text, and validation. Run before tagging a new release.

massgen/MassGen · 25 tokens

massgen-release-documenter

Guide for following MassGen's release documentation workflow. This skill should be used when preparing release documentation, updating changelogs, writing case studies, or maintaining project documentation across releases.

massgen/MassGen · 42 tokens

hive-maintainer

Discipline for developing Hive itself — PR sizing, review handling, merge discipline, release workflow, delegation, and cleanup hygiene. Use this skill when working on Hive repo changes that span multiple PRs or review cycles.

intertwine/hive-orchestrator · 48 tokens

agent-framework-py-release

Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…

microsoft/agent-framework · 103 tokens

changelog-scan

Scan merged PRs and commits since a given reference, extract titles, labels, types, and signals. Produces structured input for release notes drafting.

cobusgreyling/loop-engineering · 35 tokens