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 taurgis/sfcc-dev-mcp --skill sfcc-cartridge-developmentgit clone --depth 1 https://github.com/taurgis/sfcc-dev-mcpWrote 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/taurgis/sfcc-dev-mcp/sfcc-cartridge-development)<a href="https://agentmods.dev/skills/taurgis/sfcc-dev-mcp/sfcc-cartridge-development"><img src="https://agentmods.dev/badge/skills/taurgis/sfcc-dev-mcp/sfcc-cartridge-development/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/taurgis/sfcc-dev-mcp/sfcc-cartridge-development"><img src="https://agentmods.dev/badge/skills/taurgis/sfcc-dev-mcp/sfcc-cartridge-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.01998 |
| Opus 5 | $0.00023 | $0.00999 |
| Sonnet 5 | $0.00009 | $0.00400 |
| Haiku 4.5 | $0.00005 | $0.00200 |
Grade A, and why
sfcc-cartridge-development 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 11d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions for Creating a Salesforce B2C Commerce (SFRA) Cartridge
This document provides instructions to create, configure, and deploy a new custom cartridge for Salesforce B2C Commerce using the Storefront Reference Architecture (SFRA).
NOTE: When doing this, also consult the sfcc-sfra-controllers skill for controller development patterns and the sfcc-performance skill to ensure your cartridge follows performance optimization strategies and coding standards.
1. Core Principles
Cartridge: A cartridge is a self-contained module for code and data. It is the fundamental unit for extending functionality.
Cartridge Path: A colon-separated list of cartridge names that dictates the order of code execution. The path is searched from left to right, and the first resource found is used.
Override Mechanism: To customize functionality, create a new cartridge (e.g., app_custom_mybrand) and place it at the beginning of the cartridge path. This allows your custom files to override the base functionality without modifying the core app_storefront_base cartridge.
Example Path: app_custom_mybrand:app_storefront_base
2. Prerequisites
- Git Client: Installed and configured.
- Node.js: Version 18 is recommended for compatibility.
- SFCC Sandbox: Access to a sandbox instance, including Business Manager credentials.
- GitHub Access: Ability to clone SalesforceCommerceCloud repositories.
3. Environment Setup
Create a parent project directory.
Clone the following repositories as siblings inside the parent directory:
Note: This step is not necessary unless specifically asked for. You should only clone these if the user requests it, for most projects, there is only a need for the new cartridge that is being built - but not the entire storefront reference architecture.
# Contains the base cartridge (app_storefront_base)
git clone [email protected]:SalesforceCommerceCloud/storefront-reference-architecture.git
# Contains build and deployment scripts
git clone [email protected]:SalesforceCommerceCloud/sgmf-scripts.git
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.
- 11d ago First seen · 241 lines · 47 tokens per session scan A b01ecb5e9ea7
sfcc-cartridge-development is a skill published in the GitHub repository taurgis/sfcc-dev-mcp (28 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 1,998 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
nebula-logger-instrumentation
Use this skill when the user wants to add or update Nebula Logger instrumentation in Apex, LWC, Aura, Flow, or OmniStudio. Covers logging APIs, save patterns, record association, scenarios, tags, async transaction linking, and save method selection.
ada-diamonds-api
Reference for the Ada Diamonds public REST API (https://www.adadiamonds.com/api/v1) covering every endpoint, self-serve API keys and OAuth 2.1 scopes, the public sandbox key, rate limits, error shapes, versioning, and working curl examples. Use when integrating with Ada Diamonds over HTTP, generating client code…
salesforce
Use when working with Salesforce orgs — executing Apex, writing SOQL/SOSL, managing records, running tests, deploying metadata, or analyzing code. Guidance for the Salesforce MCP Server's tools, prompts, and resources.
sfcc-cartridge-development
Build SFRA-based Salesforce Commerce Cloud cartridges with controllers, ISML templates, and hooks to customize storefront behavior.
sfcc-ocapi-scapi
Integrate with Salesforce Commerce Cloud's headless APIs (OCAPI and Shopper APIs) to build custom storefronts and mobile commerce experiences.
sf-knowledge-api-placeorder
Apply Salesforce knowledge and best practices for Place Order REST API Developer Guide.