Borrowing it
Nothing to install: this file belongs to scrollDynasty/BrowserMesh. 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/scrollDynasty/BrowserMesh/master/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/scrollDynasty/BrowserMeshWrote 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/scrolldynasty/browsermesh/release)<a href="https://agentmods.dev/skills/scrolldynasty/browsermesh/release"><img src="https://agentmods.dev/badge/skills/scrolldynasty/browsermesh/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/scrolldynasty/browsermesh/release"><img src="https://agentmods.dev/badge/skills/scrolldynasty/browsermesh/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.00058 | $0.00963 |
| Opus 5.5 | $0.00023 | $0.00385 |
| Sonnet 5.5 | $0.00012 | $0.00193 |
| Haiku 4.5 | $0.00006 | $0.00096 |
Grade A, and why
release scanned grade A with 1 finding 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.scrollDynasty/browsermesh" How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Releasing BrowserMesh
TODO — release is currently blocked on a maintainer action
npm Trusted Publishing is not configured for the browsermesh package. This is not a code
problem and no change in this repository fixes it.
- 0.2.0 could not publish over OIDC and was pushed by hand.
publish.ymlwill fail the same way on the next version until a trusted publisher naming this repository,publish.yml, and thenpmenvironment is added on npmjs.com.- Because registry publication runs after
npm publishin the same job, it has not run either. The MCP Registry's latest entry is still 0.1.5 pointing at the oldmulti-agent-browser-mcpname.
Configuring the trusted publisher first lets the next release correct the registry on its own. Do
not work around this by publishing manually again without saying so — see
docs/IMPLEMENTATION_STATUS.md.
Also outstanding and maintainer-only: GitHub repository topics are unset.
The chain
Conventional Commit PR title
→ reviewed PR with green required checks
→ merge to master
→ release-please updates a Release PR
→ maintainer merges the Release PR
→ release-please creates the vX.Y.Z tag and GitHub Release
→ publish workflow verifies source and installed tarball
→ npm Trusted Publishing (OIDC)
→ MCP Registry publication (GitHub OIDC)
No ordinary push or feature PR publishes anything. Merging the Release PR is the only maintainer gesture that starts a release.
What bumps a version
release-please-config.json uses release-type: node with bump-minor-pre-major and
bump-patch-for-minor-pre-major. Pre-1.0, feat and fix both produce a patch. chore, docs,
ci, test, build, and refactor produce no release — use them for tooling changes that should
not cut a version.
PR titles are validated against feat fix docs refactor perf test build ci chore revert, and the
subject must start lowercase.
Version consistency
Four places carry the version and must agree: package.json, both version fields in server.json,
and the generated src/infrastructure/generated/version.ts. Release Please updates all of them via
extra-files. npm run check:version fails on drift and runs as pretypecheck, so a stale
generated module turns typecheck red before anything is type-checked.
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.
- 2mo ago First seen · 104 lines · 58 tokens per session scan A 39098314425a
release is a skill published in the GitHub repository scrollDynasty/BrowserMesh (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 58 tokens to every session and 963 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
changelog
Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
otto-drive-pr
PR mergeability, CI, and live preview.
goal-release
Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the Homebrew formula from the published release assets. Use when the user wants to draft and merge a release in one go, or…
release-dry-run
Dry run for release: summarize changes since last release and suggest version bump.