Borrowing it
Nothing to install: this file belongs to user-w-ui/search-before-build. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/user-w-ui/search-before-build/main/.agents/skills/publish-npm-release/SKILL.mdgit clone --depth 1 https://github.com/user-w-ui/search-before-buildWrote 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/user-w-ui/search-before-build/publish-npm-release)<a href="https://agentmods.dev/skills/user-w-ui/search-before-build/publish-npm-release"><img src="https://agentmods.dev/badge/skills/user-w-ui/search-before-build/publish-npm-release/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/user-w-ui/search-before-build/publish-npm-release"><img src="https://agentmods.dev/badge/skills/user-w-ui/search-before-build/publish-npm-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Tool Misuse · line 40 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Excessive Agency · line 24 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00055 | $0.00753 |
| Opus 5 | $0.00028 | $0.00377 |
| Sonnet 5 | $0.00011 | $0.00151 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
publish-npm-release 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish an npm release
Treat invocation as authority to perform the complete stable release workflow, including a Git commit, annotated tag, remote push, and npm publish. The caller has already completed product changes and updated npm authentication.
Version policy
- Read
package.jsonto obtain the package name and local version. ReadAGENTS.md, package scripts, and existing release scripts before changing anything. - Run
npm whoami, then query the registry for the package'slatestversion and complete published-version list. Handle a 404 as a first release. - Select the target version from registry evidence, never by incrementing an arbitrary local value:
- Keep the local version when it is valid SemVer, unpublished, and greater than npm
latest. - Otherwise use the next patch version after npm
latest. - If the caller explicitly requests
minorormajor, increment that component from npmlatestinstead. - Stop for prereleases unless the caller explicitly supplies the intended npm dist-tag. Do not publish a prerelease as
latestby default.
- Keep the local version when it is valid SemVer, unpublished, and greater than npm
- Update
package.jsonand every current release-metadata surface that repository validation requires to equal the target version. Prefer a repository-provided version-sync command. Otherwise inspect exact-version references and update only manifests or runtime client metadata, never historical documentation, fixtures, or changelogs.
Validate and commit
- Run all release-relevant checks documented by
AGENTS.md, package scripts, and existing release scripts. Include repository tests, syntax checks, plugin validation when present,npm pack --dry-run, andgit diff --check. - Stop before committing if any validation fails. Diagnose and fix only release/version issues; do not alter completed product behavior without asking.
- Review
git status --short. Stage only the caller's completed changes plus the release-version updates. Stop if unrelated or ambiguous changes cannot be separated safely. - Commit with
Release v<target-version>if the target-version changes are not already committed. Push the current branch and require its push to succeed before tagging.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 41 lines · 55 tokens per session scan A ee534659d991
publish-npm-release is a skill published in the GitHub repository user-w-ui/search-before-build (122 stars, last pushed 5d ago), licensed MIT. It adds 55 tokens to every session and 753 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
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.