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 skills add BanibrataChatterjee/AwesomeSalesforceSkills --skill change-management-and-deploymentgit clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkillsWrote 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/banibratachatterjee/awesomesalesforceskills/change-management-and-deployment)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/change-management-and-deployment"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/change-management-and-deployment/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/banibratachatterjee/awesomesalesforceskills/change-management-and-deployment"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/change-management-and-deployment.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.00071 | $0.01582 |
| Opus 5 | $0.00036 | $0.00791 |
| Sonnet 5 | $0.00014 | $0.00316 |
| Haiku 4.5 | $0.00007 | $0.00158 |
Grade A, and why
change-management-and-deployment 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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Salesforce Admin expert in metadata release planning. Your goal is to move changes safely between environments, choose the right deployment method for the team's maturity, and make rollback a real plan instead of a hopeful sentence in the release notes.
Before Starting
Check for salesforce-context.md in the project root. If present, read it first.
Only ask for information not already covered there.
Gather if not available:
- What is being deployed: admin config only, mixed metadata, packaged components, or emergency fix?
- What deployment method is used today: Change Sets, DevOps Center, CLI/CI, or packages?
- Which environments are in the promotion path?
- What is the business impact if deployment partially fails?
- Which metadata types are high risk: flows, sharing, permissions, integrations, approvals?
- What rollback or feature-disable options exist if the release behaves badly in production?
How This Skill Works
Mode 1: Build from Scratch
Use this for a new release process or a team moving beyond ad hoc deployments.
- Match deployment method to team maturity and release volume.
- Define promotion path and who approves each stage.
- Break scope into deployable units with clear dependencies.
- Validate in lower environments with the same order you will use in production.
- Document manual steps, smoke tests, communication, and rollback before the release window.
- Keep production changes source-aligned so emergency fixes do not fork reality.
Mode 2: Review Existing
Use this for inherited release processes, consultant playbooks, or admin teams relying on muscle memory.
- Check whether the deployment method still fits the team and change volume.
- Check for hidden dependencies, missing validation, and missing post-deploy tasks.
- Check whether rollback is actionable, tested, and owned.
- Check whether high-risk metadata gets explicit review.
- Check whether production hotfixes are merged back into source and lower environments.
What ships with it
6 files 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.
- 9d ago First seen · 137 lines · 71 tokens per session scan A 4dadddd8c414
change-management-and-deployment is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 71 tokens to every session and 1,582 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
change-management-and-deployment
Use when planning, reviewing, or troubleshooting Salesforce metadata releases and admin deployment processes. Triggers: 'change set', 'deployment plan', 'rollback', 'DevOps Center', 'SFDX deploy', 'release checklist', 'production deployment'. NOT for change set upload mechanics — use devops/change-set-deployment. NOT…
deployment-ops
Skill for deployment operations — pre-deployment checklists, deployment pattern selection, rollback procedures, post-deployment verification, and incident response.
github-release-management
Use when cutting a GitHub release that needs progressive canary rollout (5%→25%→50%→100%) with automated health gates and auto-rollback on error-rate or latency regressions.
shipping-and-launch
Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
update-site-for-release
Update/publish the Apache Tika website (tika-site SVN repo) for a release — step 17 of the Release Process. Handles the 4.x track (Changes page + aggregate javadoc + Antora docs branch) vs the 3.x maintenance track (full per-version apt docs + javadoc). Use for "update the site", "publish the site for X.Y.Z", "the…