A release procedure for publishing new versions of the salesforce-mcp-lib npm package and Salesforce 2GP package. It covers version changes, builds, tests, tags and publishing steps.

Use it when bumping versions, publishing npm or Salesforce packages, creating package versions, tagging commits or pushing a release.

It helps prevent mismatched package versions or incomplete releases when the project ships through two package systems.

How Damecek/salesforce-mcp-lib configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Damecek/salesforce-mcp-lib. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Damecek/salesforce-mcp-lib/main/.claude/skills/release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/Damecek/salesforce-mcp-lib

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/damecek/salesforce-mcp-lib/release/github.svg)](https://agentmods.dev/skills/damecek/salesforce-mcp-lib/release)

Your own site

<a href="https://agentmods.dev/skills/damecek/salesforce-mcp-lib/release"><img src="https://agentmods.dev/badge/skills/damecek/salesforce-mcp-lib/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/damecek/salesforce-mcp-lib/release"><img src="https://agentmods.dev/badge/skills/damecek/salesforce-mcp-lib/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,551 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01551
Opus 5.5	$0.00038	$0.00620
Sonnet 5.5	$0.00019	$0.00310
Haiku 4.5	$0.00010	$0.00155

Measured 9d ago against content hash 1876c09418cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 9d 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.

.claude/skills/release/SKILL.md · 147 lines

How it starts

The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.

release: Dual-Package Release Workflow

Use this skill when the user wants to release new versions of the salesforce-mcp-lib project. This project ships two packages with independent version numbers:

npm: salesforce-mcp-lib — semver in packages/salesforce-mcp-lib/package.json
SF 2GP: SalesforceMcpLib — major.minor.patch.NEXT in sfdx-project.json

Git tag format: v{npm-version}-sf{sf-version} (e.g. v2.0.0-sf2.0.0-1)

Pre-flight

Ask the user which Dev Hub owns package 0HodL0000002PQXSA2 (alias or username). No Dev Hub is hardcoded anywhere. Check with sf org list that it is authenticated. Below, <hub> means that answer. Nothing in this flow runs without the user's go.
Ask user which packages to release: both, npm only, or SF 2GP only.
Ask user the npm semver bump type: patch, minor, or major.
For SF 2GP: read sfdx-project.json → versionNumber. If the current major.minor.patch already has a promoted (released) version, it must be bumped before creating a new package version — SF will reject the create otherwise. Ask user for the SF version bump in that case.

Step-by-Step Flow

Step 1: Push pending commits

git push origin main

Ensure the working tree is clean and the release branch is up to date with origin before releasing. For 2.0.0 the work lives on feat/mcp-v2: merge it to main first (only with the user's go).

Step 2: Build & test

cd packages/salesforce-mcp-lib && npm run build && npm test && npm run lint

All tests and lint must pass. Do not proceed on failure.

Step 3: Bump npm version

cd packages/salesforce-mcp-lib && npm version <patch|minor|major> --no-git-tag-version

For 2.0.0 the version is already set in package.json, package-lock.json and sfdx-project.json (2.0.0.NEXT): skip the bump and only confirm the numbers. Otherwise this uses --no-git-tag-version so we commit the npm bump together with the SF version change in a single release commit.

Read the full file on GitHub · 147 lines

Changes

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.

9d ago Changed · +5 lines 1876c09418cc
2mo ago First seen · 142 lines · 96 tokens per session scan A 8032afee7644

Subscribe to this mod's changes

release is a skill published in the GitHub repository Damecek/salesforce-mcp-lib (19 stars, last pushed 8d ago), licensed MIT. It adds 96 tokens to every session and 1,551 once invoked, about $0.0004 per session on Opus 5.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-30.

Git and workflow Releases ai apex mcp mcp-server salesforce

release next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
releaseDamecek/salesforce-mcp-lib	Skill	19	8d ago	MIT	A	96	Claude Code
sf-knowledge-pkg2-devAvinava/sf-documentation-knowledge	Skill	4	1mo ago	none	A	22	Claude Code, Codex
release-changelog-harnessArenukvern/mcp_flutter	Skill	395	20d ago	MIT	A	84	Claude Code
polish-docs-metacyanheads/git-mcp-server	Skill	245	1mo ago	Apache-2.0	A	53	Claude Code, Codex
hmem-releaseBumblebiber/hmem	Skill	24	6d ago	MIT	A	50	Claude Code
release-managementsaidsef/mcp-github-pr-issue-analyser	Skill	6	2d ago	Apache-2.0	A	22	Claude Code, Codex
repository-manager-workspace-releaseKnuckles-Team/repository-manager	Skill	3	yesterday	MIT	A	191	Codex

salesforce-mcp-lib: Skill for Claude Code