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 agentmods add skills/kensaurus/cursor-kenji/deploy-npmnpx skills add kensaurus/cursor-kenji --skill deploy-npmgit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/deploy-npm)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/deploy-npm"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/deploy-npm.svg" alt="Measured on agentmods" 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.00050 | $0.03966 |
| Opus 5 | $0.00025 | $0.01983 |
| Sonnet 5 | $0.00010 | $0.00793 |
| Haiku 4.5 | $0.00005 | $0.00397 |
Grade A, and why
deploy-npm 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 2d 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 — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.
deploy-npm — Full release workflow
Degree of freedom: MIXED. Semver/changeset judgment [HIGH freedom];
git/gh/npm publish steps [LOW freedom — run exactly]. Never pnpm publish
locally when the repo uses Trusted Publisher.
How to reason
- Observe — branch, dirty tree, open PRs, pending changesets, release.yml trigger
- Interpret — is this a changeset-ready release or a no-op?
- Classify — proceed / stop-and-ask (dirty tree, conflicting PRs, no changeset)
- Severity — publishing the wrong bump or skipping verify is a user-facing break
Worked example
Observe: feature PR green; one minor changeset; Version PR opened by the bot; required checks never fired. Interpret: GitHub anti-loop suppressed CI on the bot branch. Classify: empty-commit to trigger CI (Phase 4), then merge Version PR. Verify:
npm viewshows the new version; do not publish from the laptop.
Self-critique before reporting
- Phase order — no publish before version PR + green CI
- Verify —
npm view(and GH Release) ran after publish, not assumed - No local publish — Trusted Publisher path only
- Right owner — running app deploy →
workflow-ship-and-observe
This skill is opinionated for repos that use:
pnpm+turbomonorepo@changesets/cli+@changesets/actionfor versioning and changelog generation- A GitHub Actions workflow named
Release(.github/workflows/release.yml) that runschangeset version+changeset publishon push tomaster - npm Trusted Publisher (OIDC) with provenance — no long-lived
NPM_TOKEN step-security/harden-runnerblocking some runner writes (notably git tag refs)
Adapt the package / branch / workflow names if the target repo differs, but keep the phase order — every phase blocks on the previous one.
Quick Start
Copy this checklist into the conversation and tick boxes as you go:
Release progress:
- [ ] Phase 0: Discover repo state (branch, open PRs, pending changesets)
- [ ] Phase 1: Author / verify the changeset
- [ ] Phase 2: Green the feature PR
- [ ] Phase 3: Merge feature PR to master
- [ ] Phase 4: Wait for & green the changesets Version PR
- [ ] Phase 5: Merge Version PR → trigger publish
- [ ] Phase 6: Handle github-actions[bot] anti-loop if push trigger didn't fire
- [ ] Phase 7: Verify on npm (npm view) and on GitHub Releases
- [ ] Phase 8: Create per-package GitHub Release notes if harden-runner blocked tags
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.
- 2d ago First seen · 401 lines · 50 tokens per session scan A e7d96ce57263
deploy-npm is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 8d ago), licensed MIT. It adds 50 tokens to every session and 3,966 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-09-03.
Other skills, from other repositories
publish
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: . Triggers: publish, release, deploy, npm publish.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.
Changelog Curator
Maintains and formats a CHANGELOG.md following Keep a Changelog conventions from git history or PR list.
Release Notes Generator
Generates clear, user-friendly release notes from a git log or list of PRs.
semantic-release-automation
Automate versioning, changelog, tags, GitHub Releases, and npm publishing from Conventional Commits with semantic-release. Use when setting up or debugging automated releases, wiring a .releaserc / release config and the plugin pipeline (commit-analyzer, release-notes-generator, changelog, npm, git, github), making…