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-figma)<a href="https://agentmods.dev/plugins/salesforcecommercecloud/b2c-developer-tooling/storefront-next-figma"><img src="https://agentmods.dev/badge/plugins/salesforcecommercecloud/b2c-developer-tooling/storefront-next-figma/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-figma"><img src="https://agentmods.dev/badge/plugins/salesforcecommercecloud/b2c-developer-tooling/storefront-next-figma.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
storefront-next-figma 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-figma",
"version": "1.3.3",
"description": "Figma design-kit skills for Storefront Next verticals — duplicate the kit, sync brand variables, and publish Code Connect. Requires the Figma MCP server.",
"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",
"figma",
"design-system",
"b2c-commerce",
"commerce-cloud"
],
"icon": "./assets/logo.png"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 87 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · +9 lines 450e2eb2ad30
- 1mo ago First seen · 12 lines scan A 2cdc80c49dde
storefront-next-figma 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
subframe
Design and build UIs with Subframe. Create pixel-perfect React + Tailwind pages using your design system, explore design variations, and implement with business logic.
web-frontend
Web development: React/Next.js best practices, web artifacts, design guidelines.
shadcn-guide
Build React UIs with shadcn/ui — the open-code component system. Covers 58+ components (Base UI and Radix variants), CLI commands, components.json configuration, CSS variable theming (OKLCH), framework installation (Next.js, Vite, Astro, Remix, Laravel, Gatsby, TanStack), registry system, form patterns (React Hook…
pencil
A design-to-development integration tool based on Pencil, a design workflow platform. It supports design workflow automation, design-system management, design review, and converting designs into React and Tailwind code.
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.