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/build-changeset)<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/build-changeset"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/build-changeset/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/build-changeset"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/build-changeset.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.00454 |
| Opus 5 | $0.00000 | $0.00227 |
| Sonnet 5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
build-changeset 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.
What it actually says
/build-changeset — Build or validate a deployment Change Set manifest
Wraps agents/changeset-builder/AGENT.md. Produces a dependency-ordered component list, destructive-changes list, and post-deploy activation checklist.
Step 1 — Collect inputs
Ask the user:
1. Mode? build | validate
2. Source org alias (required — agent verifies every named component exists)?
3. Target org alias (required — agent checks receivability + conflicts)?
4. Feature description OR artifact list?
Example: "EPIC-1472 — revenue recognition v2", or a bullet list of API names.
5. Destructive changes? (yes / no — default no; if yes, provide removal list)
If source or target org is missing, STOP.
Step 2 — Load the agent
Read agents/changeset-builder/AGENT.md + mandatory reads (devops/change-sets, devops/deployment-dependencies, devops/destructive-changes).
Step 3 — Execute the plan
- Probe source org for each named artifact.
- Enumerate implicit dependencies (profile → object, VR → object, Apex → object, etc.).
- Build a topologically-ordered component list.
- Validate mode: dry-run against target and surface conflicts.
Step 4 — Deliver the output
- Summary + confidence
- Component list (ordered)
- Dependency graph (mermaid or ASCII)
- Deployment order
- Destructive-changes list (if applicable)
- Post-deploy activation checklist
- Conflicts + unresolved refs (validate mode)
- Process Observations
- Citations
Step 5 — Recommend follow-ups
/score-deploymentbefore actually deploying/detect-drifton target org ahead of deploy/plan-release-trainif this is part of a coordinated release
What this command does NOT do
- Does not deploy.
- Does not create the Change Set in Setup — produces the plan for a human to execute.
- Does not package for 2GP / unlocked packages (out of scope).
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 · 70 lines · 0 tokens per session scan A c6d0da7ea277
build-changeset 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 454 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-08-31.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.