Borrowing it
Nothing to install: this file belongs to vKongv/chrome-browser-control. 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/vKongv/chrome-browser-control/main/.cursor/skills/npm-release/SKILL.mdgit clone --depth 1 https://github.com/vKongv/chrome-browser-controlWrote 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/vkongv/chrome-browser-control/npm-release)<a href="https://agentmods.dev/skills/vkongv/chrome-browser-control/npm-release"><img src="https://agentmods.dev/badge/skills/vkongv/chrome-browser-control/npm-release.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.00066 | $0.02025 |
| Opus 5 | $0.00033 | $0.01012 |
| Sonnet 5 | $0.00013 | $0.00405 |
| Haiku 4.5 | $0.00007 | $0.00202 |
Grade A, and why
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 5d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
chrome-browser-control — npm release
Manual semver release for the public npm package chrome-browser-control. Agents prepare and verify; humans run npm login, 2FA, and npm publish.
Detailed maintainer checklist: docs/publish-checklist.md
When to use / when NOT to use
| Use this skill | Do NOT use pbstack github-release |
|---|---|
npm package chrome-browser-control |
Web-app production deploys (gusto-be, admin FE, etc.) |
Semver tags vX.Y.Z (e.g. v0.1.1) |
Date tags YYYYMMDD-NNN |
npm publish from maintainer laptop |
Draft GitHub releases from merged-PR changelogs |
| Published (non-draft) GitHub Release after npm succeeds | Linear/client deployment summaries |
github-release compares master to last release, builds PR changelogs, and drafts releases. This repo publishes to npm first, tags vX.Y.Z on main, and ships a published GitHub Release — a different contract entirely.
Version bump checklist
Bump both files to the same semver before opening a release prep PR:
| File | Field |
|---|---|
package.json |
"version" |
extension/manifest.json |
"version" |
Also keep package-lock.json and docs/publish-checklist.md “Current release target” aligned.
Choosing the bump
Use a minor release for small changes; use a major release for large ones.
| Maintainer label | Typical scope | Semver on 0.x |
Example |
|---|---|---|---|
| Minor release | Default tweaks, skill/docs, small fixes, narrow behavior polish | Bump patch (0.Y.Z → 0.Y.Z+1) |
0.3.0 → 0.3.1 |
| Major release | New tool surfaces, architecture shifts, broad breaking defaults | Bump minor (0.Y.Z → 0.Y+1.0) |
0.3.x → 0.4.0 |
Reserve semver major (1.0.0) for a stability / public API contract milestone. When unsure, prefer a minor (patch) release.
Confirm package.json "files" still excludes skills/ (only dist, extension, package.json, README.md). The agent skill under skills/chrome-browser-control/ is not in the npm tarball — install from git or skills.sh separately.
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.
- 5d ago First seen · 205 lines · 66 tokens per session scan A 65c1d0705b46
npm-release is a skill published in the GitHub repository vKongv/chrome-browser-control (1 stars, last pushed 5d ago), licensed MIT. It adds 66 tokens to every session and 2,025 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.