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.
curl -O https://raw.githubusercontent.com/Damecek/salesforce-mcp-lib/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/Damecek/salesforce-mcp-libWrote 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/damecek/salesforce-mcp-lib/release)<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="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.00096 | $0.01299 |
| Opus 5 | $0.00048 | $0.00649 |
| Sonnet 5 | $0.00019 | $0.00260 |
| Haiku 4.5 | $0.00010 | $0.00130 |
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 7d 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 — 142 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 inpackages/salesforce-mcp-lib/package.json - SF 2GP:
SalesforceMcpLib—major.minor.patch.NEXTinsfdx-project.json
Git tag format: v{npm-version}-sf{sf-version} (e.g. v1.1.0-sf1.2.0-1)
Pre-flight
- 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 currentmajor.minor.patchalready 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 main is up to date with origin before releasing.
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
Uses --no-git-tag-version so we commit the npm bump together with the SF version change in a single release commit.
Step 4: Bump SF version in sfdx-project.json (if needed)
If the current versionNumber is already released, edit it to the new version before creating a package:
// sfdx-project.json
"versionNumber": "X.Y.Z.NEXT" // bump major.minor.patch as agreed with user
Step 5: Create SF 2GP package version
./scripts/release-create.sh --target-org mcp-lib-devhub
Critical: Always pass --target-org mcp-lib-devhub — no default devhub is configured.
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.
- 7d ago First seen · 142 lines · 96 tokens per session scan A 8032afee7644
release is a skill published in the GitHub repository Damecek/salesforce-mcp-lib (19 stars, last pushed 4mo ago), licensed MIT. It adds 96 tokens to every session and 1,299 once invoked, about $0.0005 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-30.
Other skills, from other repositories
sf-knowledge-pkg2-dev
Apply Salesforce knowledge and best practices for Second-Generation Managed Packaging Developer Guide.
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release-and-publish
Ship a release end-to-end across every registry this project targets (npm, MCP Registry). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already complete — this skill is the post-wrapup…
release-management
Tag a commit, publish a GitHub release, and read, correct or withdraw the tags and releases already there.
release-versioning
Discipline for release classification, version bumps, and changelogs, Conventional Commits classify the release range, SemVer computes the version from those commits, Keep a Changelog renders the result. Use when the user asks to cut a release, bump a version, write a changelog, decide if a change is a…
hmem-release
Pre-publish checklist for hmem: skills synced, version bumped, tests green, nothing forgotten. Use before npm publish or when the user says 'release', 'publish', 'push a release', or 'neue Version'.