agentmods.dev

score-deployment

score-deployment is a command for Claude Code from BanibrataChatterjee/AwesomeSalesforceSkills. It costs 0 tokens per session (524 once invoked), scanned A, original, Apache-2.0.

A deployment-risk command that compares a Salesforce change set with a live target org, meaning a Salesforce environment such as testing or production.

In plain words
What is it for?
It reviews metadata such as fields, Apex, flows, permissions, and sharing rules, then reports high, medium, or low risk with findings.
Why use it?
It highlights breaking changes before deployment and helps identify changes that could cause problems.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

not rated 4repo 6mo ago A scan 0 tokens original Apache-2.0

Good fit It reviews metadata such as fields, Apex, flows, permissions, and sharing rules, then reports high, medium, or low risk with findings.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/banibratachatterjee/awesomesalesforceskills/score-deployment
View source ↗ BanibrataChatterjee/AwesomeSalesforceSkills
Install

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.

Clone the repo
git clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkills

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.

agentmods badge for score-deployment

README.md
[![agentmods](https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/score-deployment/github.svg)](https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/score-deployment)
Your own site
<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/score-deployment"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/score-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.

agentmods 80×15 button for score-deployment

Your own site · 80×15
<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/score-deployment"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/score-deployment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 524 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00524
Opus 5.5 $0.00000 $0.00210
Sonnet 5.5 $0.00000 $0.00105
Haiku 4.5 $0.00000 $0.00052

Measured 2mo ago against content hash 48300af8cce4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

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.

commands/score-deployment.md · 67 lines

How it starts

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

/score-deployment — Risk-score a change set before deploy

Wraps agents/deployment-risk-scorer/AGENT.md. Compares a change set against a live target org via MCP and returns HIGH / MEDIUM / LOW risk with a breaking-change list.

Step 1 — Collect inputs (ask all three)

Ask:

1. Path to the change set?
   Example: force-app/main/default/ or a package.xml path

2. Target-org alias? (must be authenticated via sf CLI)
   Example: uat, prod

3. Change scope?
   full / delta (since last successful deploy) / a commit range

If any required input is missing, STOP.

Step 2 — Load the agent

Read agents/deployment-risk-scorer/AGENT.md fully + the devops skills and decision trees it cites.

Step 3 — Execute

Follow the 5-step plan:

  1. Enumerate metadata changes (objects, fields, Apex, LWC, Flows, VRs, profiles, sharing rules)
  2. Live-org probes (describe_org, list_custom_objects, list_flows_on_object, validate_against_org)
  3. Risk checks (field-deleted-in-use, required-field-added, VR-stricter, picklist-value-removed, API-version-downgrade, permission-revoked, trigger-added-to-covered-object, managed-package-field-override, sharing-rule-widened, flow-activated-in-deploy, test-coverage-unknown)
  4. Remediation hints per risk
  5. Pre-deploy smoke plan

Step 4 — Deliver

  • Risk score (HIGH / MEDIUM / LOW) with confidence
  • Summary table (change counts + finding counts)
  • Per-finding row (severity, item, description, remediation, skill citation)
  • Pre-deploy checklist (ordered TODOs)
  • Post-deploy smoke steps
  • Citations + any MCP tool output

Step 5 — Recommend follow-ups

  • /scan-security if any security-related finding surfaced
  • /consolidate-triggers if a new trigger was flagged for co-existence risk
  • /detect-drift after deploy to confirm the org matches the library

What this command does NOT do

  • Does not deploy.
  • Does not validate-only — recommends the user run sf project deploy validate themselves.
  • Does not override HIGH risk warnings.

Read the full file on GitHub · 67 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.

  1. 2mo ago First seen · 67 lines · 0 tokens per session scan A 48300af8cce4

Subscribe to this mod's changes

score-deployment is a command published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (4 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 524 tokens. 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.

DevOps and cloud
Related

score-deployment compared with commands from other repositories

score-deployment next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
score-deploymentBanibrataChatterjee/AwesomeSalesforceSkillsCommand46mo agoApache-2.0A0Claude Code
checklistgithub/spec-kitCommand148ktodayMITA13Claude Code
clarifygithub/spec-kitCommand148ktodayMITA27Claude Code
specifygithub/spec-kitCommand148ktodayMITA13Claude Code
analyzegithub/spec-kitCommand148ktodayMITA26Claude Code
convergegithub/spec-kitCommand148ktodayMITA35Claude Code
implementgithub/spec-kitCommand148ktodayMITA14Claude Code