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/OrcaQubits/agentic-commerce-skills-pluginsWrote 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/orcaqubits/agentic-commerce-skills-plugins/salesforce-commerce)<a href="https://agentmods.dev/plugins/orcaqubits/agentic-commerce-skills-plugins/salesforce-commerce"><img src="https://agentmods.dev/badge/plugins/orcaqubits/agentic-commerce-skills-plugins/salesforce-commerce/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/orcaqubits/agentic-commerce-skills-plugins/salesforce-commerce"><img src="https://agentmods.dev/badge/plugins/orcaqubits/agentic-commerce-skills-plugins/salesforce-commerce.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
salesforce-commerce 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 2d 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.
What it actually says
{
"name": "salesforce-commerce",
"version": "1.0.0",
"description": "Expert subagent and skills for Salesforce Commerce development — B2C Commerce Cloud (SFCC/Demandware) with SFRA cartridges, ISML templating, SCAPI/OCAPI APIs, PWA Kit headless storefronts, and B2B/D2C Commerce on Lightning with Apex hooks, LWC components, Experience Builder, Einstein AI recommendations, Salesforce Payments, and JavaScript/TypeScript/React patterns.",
"author": {
"name": "Rohit Bajaj, Julekha Khatun",
"url": "https://orcaqubits-ai.com"
},
"repository": "https://github.com/OrcaQubits/agentic-commerce-skills-plugins",
"homepage": "https://github.com/OrcaQubits/agentic-commerce-skills-plugins/tree/main/salesforce-commerce",
"keywords": [
"salesforce",
"salesforce-commerce",
"sfcc",
"commerce-cloud",
"b2c-commerce",
"b2b-commerce",
"demandware",
"sfra",
"scapi",
"ocapi",
"pwa-kit",
"cartridges",
"isml",
"apex",
"lwc",
"einstein-ai",
"salesforce-payments",
"headless-commerce",
"ecommerce"
],
"license": "MIT"
}
What it installs
The manifest is a name and a version. 22 skills, 1 agent travel with it, and installing the plugin installs all of them — 1,521 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill sf-b2b-apex A 66 tokens
- Skill sf-integrations A 62 tokens
- Skill react-patterns A 58 tokens
- Skill sf-b2c-cartridges A 63 tokens
- Skill sf-b2c-isml A 68 tokens
- Skill sf-b2c-pwa-kit A 63 tokens
- Skill sf-catalog A 61 tokens
- Skill sf-payments A 67 tokens
- Skill sf-b2b-experience A 64 tokens
- Skill sf-b2b-lwc A 58 tokens
- Skill sf-b2c-controllers A 55 tokens
- Skill sf-b2c-jobs A 63 tokens
- Skill sf-b2c-scapi A 72 tokens
- Skill sf-b2c-sfra A 59 tokens
- Skill sf-einstein A 51 tokens
- Skill sf-orders A 52 tokens
- Skill sf-setup A 69 tokens
- Skill sf-testing A 66 tokens
- Skill sf-customers A 59 tokens
- Skill sf-security A 66 tokens
- Skill sf-b2c-ocapi A 70 tokens
- Skill sf-performance A 56 tokens
- Agent salesforce-expert A 153 tokens
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.
- 2d ago First seen · 34 lines scan A 6ea9695fa375
salesforce-commerce is a plugin published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 2d ago), licensed MIT. 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-15.
Other plugins, from other repositories
internet-court
Entry point for Internet Court — the trust layer for agent-to-agent commerce. Use whenever an agent needs to transact with another agent or a paid service, or a user mentions agent payments, paid APIs (HTTP 402/x402), wallet custody or trust concerns, spending mandates, delegated permissions (ERC-7710/7715), escrow…
merchant-context
Resolve sourced merchant facts before agent commerce actions.
a2a-bridge
Bridge Claude Code with other AI coding agents (Codex, OpenClaw, Hermes, ...) through a shared daemon, push channel delivery, and bidirectional reply tooling.
humanizer
Rewrite AI-sounding text so it reads naturally 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.
themes-example
themes-example. An open-source AI agent that brings the power of Gemini directly into your terminal.