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/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/plugins/salesforcecommercecloud/b2c-developer-tooling/storefront-next)<a href="https://agentmods.dev/plugins/salesforcecommercecloud/b2c-developer-tooling/storefront-next"><img src="https://agentmods.dev/badge/plugins/salesforcecommercecloud/b2c-developer-tooling/storefront-next/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/plugins/salesforcecommercecloud/b2c-developer-tooling/storefront-next"><img src="https://agentmods.dev/badge/plugins/salesforcecommercecloud/b2c-developer-tooling/storefront-next.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
storefront-next 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 today.
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
{
"name": "storefront-next",
"version": "1.12.2",
"description": "Storefront Next development skills for building React 19 storefronts on Salesforce B2C Commerce.",
"author": {
"name": "Salesforce"
},
"homepage": "https://salesforcecommercecloud.github.io/b2c-developer-tooling/",
"repository": "https://github.com/SalesforceCommerceCloud/b2c-developer-tooling",
"license": "Apache-2.0",
"keywords": [
"salesforce",
"storefront-next",
"react",
"b2c-commerce",
"commerce-cloud",
"react-router",
"page-designer",
"scapi"
],
"icon": "./assets/logo.png"
}
What it installs
The manifest is a name and a version. 24 skills travel with it, and installing the plugin installs all of them — 4,736 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill sfnext-page-designer A 221 tokens
- Skill sfnext-components A 190 tokens
- Skill sfnext-configuration A 232 tokens
- Skill sfnext-data-fetching A 224 tokens
- Skill sfnext-scapi A 227 tokens
- Skill sfnext-accessibility A 209 tokens
- Skill sfnext-authentication A 182 tokens
- Skill sfnext-deployment A 218 tokens
- Skill sfnext-extensions A 94 tokens
- Skill sfnext-hybrid-storefronts A 194 tokens
- Skill sfnext-i18n A 174 tokens
- Skill sfnext-performance A 217 tokens
- Skill sfnext-project-setup A 200 tokens
- Skill sfnext-revalidation A 201 tokens
- Skill sfnext-routing A 231 tokens
- Skill sfnext-security A 186 tokens
- Skill sfnext-testing A 208 tokens
- Skill sfnext-theming A 194 tokens
- Skill sfnext-analytics-consent A 179 tokens
- Skill sfnext-commerce-features A 215 tokens
- Skill sfnext-overview A 166 tokens
- Skill sfnext-seo A 195 tokens
- Skill sfnext-state-management A 190 tokens
- Skill sfnext-quality-gates A 189 tokens
What ships with it
1 file beside plugin.json 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.
- today Changed · +11 lines 653471ebab31
- 3d ago Changed 8a362428556f
- 7d ago Changed 3fd1ac7cb988
- 12d ago Changed bca7bfb89a1f
- 14d ago Changed dada19d87f97
- 20d ago Changed b1affffcfe29
- 21d ago Changed 9015f0a31319
- 25d ago Changed ed115bc800ba
- 1mo ago Changed b119ab6ac988
- 1mo ago First seen · 12 lines scan A f887fd39923f
storefront-next is a plugin published in the GitHub repository SalesforceCommerceCloud/b2c-developer-tooling (56 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
shopify
Manage Shopify stores: product creation, bulk imports, content pages, blog posts, and SEO metadata.
stripekit
Reconcile your Stripe catalog (products, prices, webhook, portal) and inspect your account — exposed to Claude as MCP tools.
shopify-app-skill
Production patterns for embedded Shopify apps with React Router v7, DynamoDB single-table design, Lambda, SQS, CDK.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.