Borrowing it
Nothing to install: this file belongs to SecretRichGarden/metasota-API-MCP. 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/SecretRichGarden/metasota-API-MCP/main/.codex/skills/nodejs-npm-auto-release/SKILL.mdgit clone --depth 1 https://github.com/SecretRichGarden/metasota-API-MCPWrote 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/secretrichgarden/metasota-api-mcp/nodejs-npm-auto-release)<a href="https://agentmods.dev/skills/secretrichgarden/metasota-api-mcp/nodejs-npm-auto-release"><img src="https://agentmods.dev/badge/skills/secretrichgarden/metasota-api-mcp/nodejs-npm-auto-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/secretrichgarden/metasota-api-mcp/nodejs-npm-auto-release"><img src="https://agentmods.dev/badge/skills/secretrichgarden/metasota-api-mcp/nodejs-npm-auto-release.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.00063 | $0.00756 |
| Opus 5 | $0.00032 | $0.00378 |
| Sonnet 5 | $0.00013 | $0.00151 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
nodejs-npm-auto-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 12d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Node.js NPM Auto Release
Overview
Provide a repeatable workflow to prepare, verify, and ship npm packages with a combined auto-version-and-publish GitHub Action, plus local checks before push.
Setup Checklist
- Add release scripts in
package.json
{
"scripts": {
"release:patch": "npm version patch -m \"chore(release): v%s\"",
"release:minor": "npm version minor -m \"chore(release): v%s\"",
"release:major": "npm version major -m \"chore(release): v%s\""
}
}
- Add
.npmignoreto keep packages clean
Typical entries:
.github/.claude/docs/tests/.envnode_modules/
- Add the combined workflow file
Create .github/workflows/auto-version-publish.yml with:
name: auto version and publish
on:
push:
branches:
- main
permissions:
contents: write
id-token: write
jobs:
release:
if: ${{ !contains(github.event.head_commit.message, 'chore(release):') }}
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
with:
fetch-depth: 0
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: "18"
registry-url: "https://registry.npmjs.org"
- name: Install dependencies
run: |
npm ci
- name: Typecheck
run: |
npm run typecheck
- name: Test
run: |
npm test
- name: Configure git
run: |
git config user.name "github-actions[bot]"
git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
- name: Bump patch version and tag
run: |
npm version patch -m "chore(release): v%s [skip ci]"
- name: Push version bump and tag
run: |
git push origin HEAD:main --follow-tags
- name: Publish
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
run: |
npm publish --access public
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.
- 12d ago First seen · 136 lines · 63 tokens per session scan A ce59b46d5432
nodejs-npm-auto-release is a skill published in the GitHub repository SecretRichGarden/metasota-API-MCP (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 63 tokens to every session and 756 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-31.
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.