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/webmcp-org/npm-packages/releasenpx skills add WebMCP-org/npm-packages --skill releasegit clone --depth 1 https://github.com/WebMCP-org/npm-packagesWrote 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/webmcp-org/npm-packages/release)<a href="https://agentmods.dev/skills/webmcp-org/npm-packages/release"><img src="https://agentmods.dev/badge/skills/webmcp-org/npm-packages/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 | $0.00079 | $0.03032 |
| Opus 5 | $0.00039 | $0.01516 |
| Sonnet 5 | $0.00016 | $0.00606 |
| Haiku 4.5 | $0.00008 | $0.00303 |
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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -I "https://install.mcp-b.ai/webmcp-local-relay-$VERSION.mcpb" How it starts
The opening of the file, as written. The whole thing — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Skill for @mcp-b Packages
Publish packages from this monorepo to npm using changesets and pnpm publish -r.
Read references/publishing.md for package-specific build, authentication, MCPB, and troubleshooting notes.
CRITICAL: Always Use Changesets
NEVER manually edit package.json versions. Manual bumps skip CHANGELOG generation, which means published versions have no record of what changed. This has happened before and must not happen again.
The ONLY exception is snapshot prereleases (see below), whose versions are never committed.
Release Flow (Step by Step)
Follow these steps in order. Do not skip steps.
Step 1: Validate
pnpm build && pnpm typecheck && vp check && pnpm test:unit && pnpm release:check
Stop if anything fails. Fix it first.
Step 2: Create Changeset
pnpm changeset
This is interactive. It will ask:
- Which packages changed? Select only the ones with actual code changes.
- What kind of bump? (patch / minor / major)
- Summary of changes? Write a clear description.
This creates a .changeset/<random-name>.md file. You can create multiple changesets
for different changes before releasing.
Use separate changesets when packages need different release notes. A multi-package changeset copies the same summary into every selected package's changelog.
Fixed versioning note: Select only packages that actually changed. Changesets automatically bumps all packages in the configured fixed group to the same new version, which is now every published package.
Step 3: Apply Version Bumps
pnpm changeset:version
This does four things:
- Bumps each selected package and every package in its fixed group
- Generates
CHANGELOG.mdentries from the changeset summaries - Deletes the consumed
.changeset/*.mdfiles - Synchronizes checked-in release metadata with the package versions
Step 4: Review
# Check version bumps
git diff packages/*/package.json
# Check generated changelogs
git diff packages/*/CHANGELOG.md
# Check synchronized metadata
git diff packages/webmcp-local-relay/manifest.json packages/global/test-unpkg.html
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.
- 5d ago First seen · 333 lines · 79 tokens per session scan A 8a4f6923afce
release is a skill published in the GitHub repository WebMCP-org/npm-packages (80 stars, last pushed 5d ago), licensed MIT. It adds 79 tokens to every session and 3,032 once invoked, about $0.0004 per session on Opus 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-30.
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.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…