Borrowing it
Nothing to install: this file belongs to jd-solanki/airig. 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/jd-solanki/airig/main/.ai/skills/automate-npm-release/SKILL.mdgit clone --depth 1 https://github.com/jd-solanki/airigWrote 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/jd-solanki/airig/automate-npm-release)<a href="https://agentmods.dev/skills/jd-solanki/airig/automate-npm-release"><img src="https://agentmods.dev/badge/skills/jd-solanki/airig/automate-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/jd-solanki/airig/automate-npm-release"><img src="https://agentmods.dev/badge/skills/jd-solanki/airig/automate-npm-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.00096 | $0.00536 |
| Opus 5 | $0.00048 | $0.00268 |
| Sonnet 5 | $0.00019 | $0.00107 |
| Haiku 4.5 | $0.00010 | $0.00054 |
Grade A, and why
automate-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.
What it actually says
Automate npm Release
Use this skill to set up npm release automation. First identify the repository shape, then load the matching reference:
- Single publishable package: see SINGLE_PACKAGE.md.
- Workspace monorepo with independently published packages: see MONOREPO.md.
Shared rules
- npm requires the first publish to be done manually for each public package:
npm publish --access public
- Prefer npm trusted publishing/OIDC when the project asks for it. Configure the package on npmjs.com after the first manual publish, then use
id-token: writein GitHub Actions. Ensurepackage.jsonhasrepository.urlexactly matching the GitHub repo URL (case-sensitive) — required for provenance validation. - If using token-based publishing, configure
actions/setup-nodewithregistry-url: https://registry.npmjs.orgsoNODE_AUTH_TOKENcan authenticatenpm publish. - In pnpm workspaces, publish via
pnpm packfollowed bynpm publish <tarball> --access public. This lets pnpm rewriteworkspace:*dependencies while npm handles trusted publishing/OIDC. Use changelogithub only for GitHub release notes/releases. - Always run checks, tests, and package builds before publishing.
- Keep the private workspace root unpublished; publish from the actual package directory.
Quick choice
Use single-package release automation when one package.json owns the npm artifact and one v* tag maps to one package.
Use monorepo release automation when multiple workspace packages publish independently. In that flow, tags must encode the package, such as cli-v0.1.0, and GitHub release-note generation must use explicit previous same-package tag ranges.
Workflow examples
- EXAMPLE_WORKFLOW.yml — single-package token/provenance workflow.
- MONOREPO_WORKFLOW.yml — package-scoped monorepo workflow using trusted publishing and changelogithub.
What ships with it
4 files 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 · 38 lines · 96 tokens per session scan A e89a9721b2df
automate-npm-release is a skill published in the GitHub repository jd-solanki/airig (2 stars, last pushed 2mo ago), licensed MIT. It adds 96 tokens to every session and 536 once invoked, about $0.0005 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
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack).
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
releasepr
Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.