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/b2c-cli)<a href="https://agentmods.dev/plugins/salesforcecommercecloud/b2c-developer-tooling/b2c-cli"><img src="https://agentmods.dev/badge/plugins/salesforcecommercecloud/b2c-developer-tooling/b2c-cli/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/b2c-cli"><img src="https://agentmods.dev/badge/plugins/salesforcecommercecloud/b2c-developer-tooling/b2c-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
b2c-cli 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": "b2c-cli",
"version": "1.12.2",
"description": "B2C CLI Skills for Salesforce Commerce Cloud development.",
"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",
"b2c-commerce",
"commerce-cloud",
"sfra",
"scapi",
"ocapi"
],
"icon": "./assets/logo.png"
}
What it installs
The manifest is a name and a version. 22 skills travel with it, and installing the plugin installs all of them — 2,152 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill b2c-config A 46 tokens
- Skill b2c-docs A 170 tokens
- Skill b2c-import-set-migrations A 89 tokens
- Skill b2c-metrics A 107 tokens
- Skill b2c-bm-users-roles A 161 tokens
- Skill b2c-logs A 100 tokens
- Skill b2c-mrt A 77 tokens
- Skill b2c-am A 137 tokens
- Skill b2c-content A 104 tokens
- Skill b2c-slas A 102 tokens
- Skill b2c-cap A 140 tokens
- Skill b2c-cip A 48 tokens
- Skill b2c-code A 112 tokens
- Skill b2c-debug A 110 tokens
- Skill b2c-webdav A 99 tokens
- Skill b2c-ecdn A 109 tokens
- Skill b2c-sandbox A 78 tokens
- Skill b2c-scapi-custom A 84 tokens
- Skill b2c-sites A 115 tokens
- Skill b2c-site-import-export A 33 tokens
- Skill b2c-job A 33 tokens
- Skill b2c-scapi-schemas A 98 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 · +9 lines 4fdd1aeb4452
- 3d ago Changed c0327aa8f88b
- 7d ago Changed 3a4e0a2469fe
- 12d ago Changed e665fa7c550f
- 14d ago Changed caf504324997
- 20d ago Changed d4ec1509221c
- 21d ago Changed c33ab3b39e05
- 25d ago Changed 63adf8565192
- 1mo ago Changed 3bb08e0b781c
- 1mo ago First seen · 12 lines scan A 652e637bbce1
b2c-cli 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
stripekit
Reconcile your Stripe catalog (products, prices, webhook, portal) and inspect your account — exposed to Claude as MCP tools.
agent-deck
Complete guide for managing AI coding agent sessions via agent-deck CLI - session lifecycle, MCP management, groups, profiles, and automation.
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.
themes-example
themes-example. An open-source AI agent that brings the power of Gemini directly into your terminal.