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.
git 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/commands/banibratachatterjee/awesomesalesforceskills/score-deployment)<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.
<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>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.00000 | $0.00524 |
| Opus 5 | $0.00000 | $0.00262 |
| Sonnet 5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00052 |
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 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 — 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:
- Enumerate metadata changes (objects, fields, Apex, LWC, Flows, VRs, profiles, sharing rules)
- Live-org probes (
describe_org,list_custom_objects,list_flows_on_object,validate_against_org) - 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)
- Remediation hints per risk
- 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-securityif any security-related finding surfaced/consolidate-triggersif a new trigger was flagged for co-existence risk/detect-driftafter 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 validatethemselves. - Does not override HIGH risk warnings.
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 · 67 lines · 0 tokens per session scan A 48300af8cce4
score-deployment is a command published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.