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.
npx skills add metarhia/metaskills --skill npm-publishgit clone --depth 1 https://github.com/metarhia/metaskillsWrote 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.
[](https://agentmods.dev/skills/metarhia/metaskills/npm-publish)<a href="https://agentmods.dev/skills/metarhia/metaskills/npm-publish"><img src="https://agentmods.dev/badge/skills/metarhia/metaskills/npm-publish/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.
<a href="https://agentmods.dev/skills/metarhia/metaskills/npm-publish"><img src="https://agentmods.dev/badge/skills/metarhia/metaskills/npm-publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 103 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00059 | $0.01690 |
| Opus 5 | $0.00030 | $0.00845 |
| Sonnet 5 | $0.00012 | $0.00338 |
| Haiku 4.5 | $0.00006 | $0.00169 |
Grade A, and why
npm-publish 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
npm Publish Preparation
Systematic workflow for preparing an npm package for a new release. Every step must pass before proceeding to the next.
Step 0: Gather Release Intent
Ask the user (use AskQuestion if available):
- Version bump type: patch / minor / major / explicit version / prerelease tag
- Prerelease label (if any): e.g.
alpha,beta,rc,prerelease - Confirm changelog entries: ask if the
[Unreleased]section in CHANGELOG is complete, or if the user wants to draft entries from recent commits
If the user already specified intent (e.g. "prepare 4.1.0 release"), skip the question and proceed.
Step 1: Pre-flight Checks
Run:
npm i # install deps
npm test # must exit 0 (lint + types + tests)
Then in parallel: npm outdated and npm audit (report to user).
If npm test fails, stop and fix issues before continuing.
Step 2: Version Bump
Read current version from package.json
Compute the new version based on user intent and semver rules:
- patch:
1.2.3→1.2.4 - minor:
1.2.3→1.3.0 - major:
1.2.3→2.0.0 - prerelease:
1.2.3→1.2.4-<label>.0, or1.2.4-beta.0→1.2.4-beta.1 - Removing prerelease tag:
4.0.3-prerelease→4.0.3(just strip the suffix)
Update "version" in package.json using StrReplace (not npm version — we manage changelog manually).
Step 3: Update CHANGELOG.md
The changelog uses:
- Sections:
## [Unreleased]at top;## [Version] - YYYY-MM-DDfor releases (date in ISO 8601) - Order: newest first; every version gets an entry
- Types of changes:
Added,Changed,Deprecated,Removed,Fixed,Security. Group same-type changes under each - Entries: bullet lists; past tense; capitalise first letter; human-readable, curated (no raw git diffs)
- Links: footnote-style link block at bottom:
[unreleased]: ...,[version]: ...(GitHub compare URLs) - Principles: changelog is for humans; omit empty sections; call out breaking changes and deprecations clearly
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.
- 11d ago First seen · 191 lines · 59 tokens per session scan A 7ef2f9069dbb
npm-publish is a skill published in the GitHub repository metarhia/metaskills (50 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 1,690 once invoked, about $0.0003 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.
Other skills, from other repositories
zb-release-pipeline
Generate a GitHub Actions pipeline that builds a zb (Zero Dependencies Builder) project and publishes a GitHub Release with the produced JAR. Use whenever the user wants CI/CD, a build pipeline, a release workflow, or GitHub Actions for a zb-based Java project — phrases like "set up GitHub Actions for this zb…
changelog
Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.
ship
Enter the Ship phase of CocoBrew. Reads review.md approval, generates structured commit, creates semantic version tag, optionally creates PR via gh CLI, and records deployment details. Requires approved review.
changelog
Update per-package CHANGELOG.md files for a Ratel release. Drafts entries with git-cliff (scoped per package), lets you curate, then writes the CHANGELOGs. Handles both RC entries and GA-graduation collapse (merging X.Y.Z-rc. sections into a single X.Y.Z section). Invoke before tagging a release.
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
release-management
Automates GitHub releases with semantic versioning, changelog generation from merged PRs, and gh CLI integration. Supports draft, prerelease, and standard release workflows with task-tracked multi-phase execution. Use when creating releases, tagging versions, or publishing changelogs.