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 SalesforceCommerceCloud/b2c-developer-tooling --skill sfnext-commerce-featuresgit clone --depth 1 https://github.com/SalesforceCommerceCloud/b2c-developer-toolingWrote 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/salesforcecommercecloud/b2c-developer-tooling/sfnext-commerce-features)<a href="https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-commerce-features"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-commerce-features/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/salesforcecommercecloud/b2c-developer-tooling/sfnext-commerce-features"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-commerce-features.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.00215 | $0.01500 |
| Opus 5.5 | $0.00086 | $0.00600 |
| Sonnet 5.5 | $0.00043 | $0.00300 |
| Haiku 4.5 | $0.00021 | $0.00150 |
Grade A, and why
sfnext-commerce-features 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 15d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Storefront Next Commerce Features
Start with the feature table, then read the named doc in your project's docs/ folder. Do not assume a feature is live: several ship as UI scaffolds with mock data (see Feature stubs).
Feature table
| Feature | Enable with | Also needs | Read |
|---|---|---|---|
| Shopper Context | features.shopperContext.enabled (env: PUBLIC__app__features__shopperContext__enabled=true), default off |
Shopper Context API access for the SLAS client; qualifiers arrive as URL params or via the useShopperContext hook, stored in cookies |
docs/README-SHOPPER-CONTEXT.md |
| Returns, cancel, tracking (Order Management) | Nothing to toggle | Salesforce Order Management connected to the B2C instance; order loader expands ['oms','oms_shipments']; without omsData only tracking shows |
docs/README-ORDER-MANAGEMENT.md |
| Delivery estimates | Keep extension SFDC_EXT_SHIPPING_DELIVERY installed |
SLAS scopes sfcc.shopper-delivery-estimates and sfcc.shopper-standard, a delivery-estimate Commerce App bound to sfcc.app.shipping.estimate, online products on the site |
docs/README-DELIVERY-ESTIMATES.md |
| Guest order lookup | guestOrderLookup.enabled: true in config.server.ts |
GUEST_ORDER_LOOKUP_COOKIE_SECRET (or CLIENT_SECRET fallback) and a cartridge implementing hook sfcc.app.order.sendOrderAccessCode to email the code |
docs/README-GUEST-ORDER-LOOKUP.md |
Email cartridge (app_storefrontnext_base) |
Deploy cartridge, add to site cartridge path | SLAS scope c_sfnext_notify (sfnext setup-base-cartridge --slas-client-id <id>), import preference metadata, set Storefront Hosts global custom preference, callback mode in storefront config |
docs/README-EMAIL-CARTRIDGE.md |
| Feature stubs | n/a | Mock UI scaffolds, not integrations | docs/README-FEATURE-STUBS.md |
Extensions shipped in src/extensions
Registry: src/extensions/config.json (keys SFDC_EXT_*). Each extension contributes components to UITarget points through its target-config.json. To install or remove one, follow the install/uninstall instructions in instructions/*.mdc when the registry entry references them; building new extensions is storefront-next:sfnext-extensions.
What ships with it
2 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.
- 15d ago First seen · 68 lines · 215 tokens per session scan A 913d331d0d9b
sfnext-commerce-features is a skill published in the GitHub repository SalesforceCommerceCloud/b2c-developer-tooling (56 stars, last pushed today), licensed Apache-2.0. It adds 215 tokens to every session and 1,500 once invoked, about $0.0009 per session on Opus 5.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-10-05.
Other skills, from other repositories
shopping
Skill "shopping" from Hmbown/Codewhale, covering shopping, when to use, setup, workflow and non-goals.
daiso-cli
A command-line interface for searching Daiso and related Korean shopping, store, food, cinema, and convenience-store data through the Daiso project. It can return structured JSON for searches and comparisons.
goofish-publish-item
A workflow for publishing second-hand items on Xianyu, a Chinese marketplace for used goods. It turns an item description and images into a category, title, listing text, and a ready-to-submit listing.
goofish-reply-buyer
A Chinese-language workflow for handling buyer messages on Xianyu, a Chinese second-hand marketplace. It reviews conversations, classifies buyer intent, and drafts replies according to the seller’s rules, but waits for human approval before sending.
goofish-shop-diagnosis
A read-only diagnostic workflow for Xianyu shops and listings. It compares how a shop’s items appear in marketplace search with their stored details to investigate visibility and sales problems.
booking-cli
Searches Booking.com from the terminal via cli-web-booking — find hotels, apartments, and hostels by destination, dates, and guests; get property details by slug; resolve destination names to IDs. Use when the user asks about Booking.com, hotel search, accommodation prices, property ratings, or comparing places to…