Borrowing it
Nothing to install: this file belongs to flowing-abyss/obsidian-hybrid-search. 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/flowing-abyss/obsidian-hybrid-search/master/.ai/skills/releasing-an-npm-package/SKILL.mdgit clone --depth 1 https://github.com/flowing-abyss/obsidian-hybrid-searchWrote 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/flowing-abyss/obsidian-hybrid-search/releasing-an-npm-package)<a href="https://agentmods.dev/skills/flowing-abyss/obsidian-hybrid-search/releasing-an-npm-package"><img src="https://agentmods.dev/badge/skills/flowing-abyss/obsidian-hybrid-search/releasing-an-npm-package/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/flowing-abyss/obsidian-hybrid-search/releasing-an-npm-package"><img src="https://agentmods.dev/badge/skills/flowing-abyss/obsidian-hybrid-search/releasing-an-npm-package.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00033 | $0.00309 |
| Opus 5.5 | $0.00013 | $0.00124 |
| Sonnet 5.5 | $0.00007 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
releasing-an-npm-package 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 today.
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.
What it actually says
Releasing the npm package
Read package.json, server.json, and the current GitHub release workflow
before changing metadata. Use the
requested version and preserve the package's supported Node and platform matrix.
Run the canonical completion checks and inspect the package file list before
committing release metadata. Do not publish development tooling, fixtures,
credentials, or local vault content.
Synchronize package.json, the lockfile, and server.json before tagging. This
repository uses the following sequence after verification:
npm version X.Y.Z --no-git-tag-version
npm run sync-server-json
git add package.json package-lock.json server.json
git commit -m "chore(release): X.Y.Z"
git push origin master
git tag vX.Y.Z
git push origin vX.Y.Z
The tag must name the same commit as the synchronized version files. Push and publish only within the user's explicit release authorization.
A tag push starts the release workflow. Confirm CI passed on that exact commit, then check the GitHub release and npm version before reporting publication. If a workflow fails after a tag or version is public, inspect its failure and repair that release. Do not blindly rerun a version bump or create another tag. Describe user-facing changes and compatibility requirements with humanizer.
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.
- today First seen · 36 lines · 33 tokens per session scan A 6061febc7174
releasing-an-npm-package is a skill published in the GitHub repository flowing-abyss/obsidian-hybrid-search (113 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 309 once invoked, about $0.0001 per session on Opus 5.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-10-24.
Other skills, from other repositories
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
github-cli
A command-line tool connection for GitHub tasks that built-in tools do not cover. It uses GitHub's command-line program to work with issues, pull requests, releases, workflows, searches, and the GitHub API.
release-slice
Open-source one slice of a private system: take a component, sanitize it, run a leak-scan as a hard gate, publish to GitHub, then changelog, roadmap and tag on cadence, then the content wave. Publishing without passing the leak-scan is forbidden. Triggers: "/release-slice ", "ship the next slice".
release-app
Cut a workhub release — bump the app version, write the changelog entry, commit to main, tag vX.Y.Z, push, and verify the GitHub Release published with every required asset. Use when the user wants to release or ship the workhub app, tag a version, or publish a build.