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 commerce-checkout-flow-designgit 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/commerce-checkout-flow-design)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/commerce-checkout-flow-design"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/commerce-checkout-flow-design/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/commerce-checkout-flow-design"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/commerce-checkout-flow-design.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.00123 | $0.04114 |
| Opus 5 | $0.00062 | $0.02057 |
| Sonnet 5 | $0.00025 | $0.00823 |
| Haiku 4.5 | $0.00012 | $0.00411 |
Grade A, and why
commerce-checkout-flow-design 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commerce Checkout Flow Design
This skill activates when a practitioner or project team needs to define, scope, or document the checkout experience for a Salesforce B2B or D2C Commerce storefront before any implementation begins. It covers runtime model selection, UX step design, payment option scoping, shipping rule definition, and guest versus registered buyer experience planning. It does not cover implementation: Apex adapter code, CartCheckoutSession debugging, Extension Point class registration, or Flow Builder element configuration are handled by commerce-checkout-configuration.
Before Starting
Gather this context before working on anything in this domain:
- Store template type. The single most consequential design decision is whether the store uses the LWR template (Managed Checkout) or the Aura template (Flow Builder checkout). These are mutually exclusive runtime models with entirely different customization surfaces. If the store template has not yet been chosen, this skill must help make that selection first — everything else flows from it.
- Buyer personas. Confirm whether the storefront will serve registered authenticated buyers, guest (unauthenticated) buyers, or both. Guest checkout requires different data collection requirements at every step and imposes additional platform permissions that must be planned for.
- Payment landscape. Identify all payment methods the business needs to support at launch and near-term. Each non-native payment method requires a custom Apex Payment Adapter. Knowing the full list upfront prevents surprise scope additions mid-build.
- Shipping model. Determine whether shipping rates come from an external carrier API, a flat rate table, free shipping with conditions, or a mix. External carrier rate calls introduce async latency constraints that must be accounted for in the UX design.
- B2B-specific concerns. B2B Commerce introduces purchase order (PO) payment, account-level pricing, and optional buyer approval workflows before order submission. These are design concerns that must be scoped before configuration begins.
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 · 235 lines · 123 tokens per session scan A 665174b4344b
commerce-checkout-flow-design is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 123 tokens to every session and 4,114 once invoked, about $0.0006 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
commerce-checkout-flow-design
Use this skill when designing the checkout experience for a Salesforce B2B or D2C Commerce storefront — covering runtime model selection (LWR Managed Checkout vs Aura Flow Builder), cart and line-item requirements, payment option scoping, shipping rule definition, and guest vs. registered buyer experience design.…
commerce-checkout-configuration
Use this skill when configuring Salesforce B2B or D2C Commerce checkout: payment methods, shipping/tax integration, guest checkout, order summary setup, and CartCheckoutSession state orchestration. Trigger keywords: checkout flow, payment adapter, shipping tax integration, guest checkout, order summary…
commerce-pricing-and-promotions
Configure pricebooks, tiered pricing, promotions, coupon codes, and cart discounts for B2B or D2C Commerce stores. Trigger keywords: WebStorePricebook, BuyerGroupPricebook, PriceAdjustmentSchedule, PromotionsCartCalculator, commerce coupon, cart-level discount, tiered price, Commerce promotion. NOT for Sales Cloud…
b2b-vs-b2c-requirements
Use this skill to determine whether a Salesforce Commerce project should use B2B Commerce (account-gated, BuyerGroup-based, contract pricing) or D2C Commerce (consumer storefront, guest checkout, individual-based). Trigger keywords: B2B vs B2C, commerce platform selection, buyer journey, account-based purchasing…
commerce-catalog-strategy
Use this skill when designing a product catalog taxonomy, planning attribute strategy, or determining search and navigation structure for a B2B or B2C/D2C Commerce store. Triggers on: taxonomy design questions, attribute planning, search index strategy, category navigation structure, or merchandising hierarchy…
moonpay-commerce
Browse Shopify stores, search products, manage a cart, and checkout with crypto via Solana Pay. No login required.