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/plan-release-train)<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/plan-release-train"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/plan-release-train/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/plan-release-train"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/plan-release-train.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.00340 |
| Opus 5 | $0.00000 | $0.00170 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
plan-release-train 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 10d 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
/plan-release-train — Plan or audit a Salesforce release train
Wraps agents/release-train-planner/AGENT.md. Produces package strategy, branching model, environment promotion path, release calendar, CI/CD gates, and hotfix playbook.
Step 1 — Collect inputs
1. Mode? design | audit
2. Team size?
3. Release cadence? weekly / biweekly / monthly / quarterly
4. Package strategy (optional)? unlocked / 2gp-managed / org-dependent / metadata-only
5. Customer count (optional)? 1 for internal, N for ISV
6. Regions (optional)?
Step 2 — Load the agent
Read agents/release-train-planner/AGENT.md + mandatory reads.
Step 3 — Execute the plan
Package choice → branching model → environment path → calendar (with Platform freezes) → CI/CD gates → hotfix → (audit) git diff vs stated model.
Step 4 — Deliver the output
Summary, package strategy, branching model, promotion table, 180-day calendar, CI/CD gates, hotfix playbook, audit findings, Process Observations, citations.
Step 5 — Recommend follow-ups
/design-sandbox-strategyfor refresh cadence alignment/assess-waffor NFR coverage
What this command does NOT do
- Does not cut branches, tag releases, or deploy packages.
- Does not run CI pipelines.
- Does not set up DevOps tooling (plan only).
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.
- 10d ago First seen · 40 lines · 0 tokens per session scan A ec7731622fce
plan-release-train 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 340 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
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
check-release-health
Summarize the CI health of an OpenShift release using live data from the openshift-ci-mcp server.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
cf-scaffold-project
Scaffold a Cloudflare project — Worker, Pages, or Worker+D1+R2 starter — with Wrangler config, Terraform skeleton, and GitHub Actions deploy using scoped API tokens.