Borrowing it
Nothing to install: this file belongs to SalesforceCommerceCloud/b2c-developer-tooling. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SalesforceCommerceCloud/b2c-developer-tooling/main/.agents/skills/mcp-development/SKILL.mdgit 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/mcp-development)<a href="https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/mcp-development"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/mcp-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/salesforcecommercecloud/b2c-developer-tooling/mcp-development"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/mcp-development.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.00039 | $0.03092 |
| Opus 5.5 | $0.00016 | $0.01237 |
| Sonnet 5.5 | $0.00008 | $0.00618 |
| Haiku 4.5 | $0.00004 | $0.00309 |
Grade A, and why
mcp-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 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
B2C MCP Development
Scope and owners
packages/b2c-dx-mcp: tool registration, adapters, resources, and session lifecycles.- SDK
guidance: shared offline catalog, search, section reads, and exposure filters. packages/b2c-dx-mcp/skills: shipped MCP skills and collection manifest. Native collections live underskills/.docs/mcp: user capabilities, installation, configuration, and security. Tool references use capability/tool-name tables with shared access requirements. Keep parameters and agent choreography in schemas and skills. Lead public setup with the agent plugin for compatible clients; put direct registration and toolset customization second. Lead capabilities with developer tasks, followed by administrator/merchant use cases and example prompts. Use a short product description followed immediately by quick install. Put full client setup on Installation and optional launch defaults under advanced manual configuration. Public prose explains user outcomes, setup, access, and limitations; omit routine agent decisions, discovery, and invocation procedures. Changing a tool name to "ask your assistant" does not make agent choreography user-facing. Keep tool names in reference tables and customization examples. Sidebar labels identify destinations tersely (Introduction, Installation, Tool Reference); page headings can be more descriptive. Order navigation by user tasks and reuse the same MCP navigation across site sections. Explain included native skills by linking to the Agent Skills & Plugins catalog. MCP-specific operating skills are agent instructions, not a public capability needing a separate page. Name the platform B2C Commerce in public prose; preserve official product names such as Salesforce Commerce API.
For skill/runbook content, read workflow authoring. For packaging and protocol details, read the catalog contract.
Native skill changes use an agent-plugin changeset; the MCP's bundled
workspace:* dependency automatically triggers an MCP patch release. Keep it in
dependencies and bundledDependencies, not devDependencies. MCP-specific
skills and collection changes need an MCP changeset.
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 Changed · +10 lines 52f88c706bd7
- 23d ago Changed · +9 lines d2674c1cf221
- 1mo ago Changed · +4 lines ac3f18693457
- 1mo ago Changed · +35 lines cae77d5d6d78
- 1mo ago First seen · 184 lines · 39 tokens per session scan A 37c3ebd7cca2
mcp-development is a skill published in the GitHub repository SalesforceCommerceCloud/b2c-developer-tooling (56 stars, last pushed yesterday), licensed Apache-2.0. It adds 39 tokens to every session and 3,092 once invoked, about $0.0002 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-09-12.
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…