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.
npx skills add OrcaQubits/agentic-commerce-skills-plugins --skill sf-b2c-ocapigit 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/skills/orcaqubits/agentic-commerce-skills-plugins/sf-b2c-ocapi)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/sf-b2c-ocapi"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/sf-b2c-ocapi/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/orcaqubits/agentic-commerce-skills-plugins/sf-b2c-ocapi"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/sf-b2c-ocapi.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.00070 | $0.01438 |
| Opus 5 | $0.00035 | $0.00719 |
| Sonnet 5 | $0.00014 | $0.00288 |
| Haiku 4.5 | $0.00007 | $0.00144 |
Grade A, and why
sf-b2c-ocapi 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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OCAPI -- Open Commerce API (Maintenance-Only)
MAINTENANCE-ONLY NOTICE
OCAPI is in maintenance-only mode. Salesforce is not adding new features and has positioned SCAPI as the successor for all new storefront development. OCAPI receives only critical security patches and bug fixes. It has NOT been formally deprecated with a sunset date.
Use this skill ONLY for: maintaining legacy integrations, planning OCAPI-to-SCAPI migration, or debugging production OCAPI issues.
Do NOT build new features against OCAPI. Use the
sf-b2c-scapiskill for all new work.
Before Writing Code
Fetch live documentation BEFORE writing any code.
- Web-search
site:developer.salesforce.com OCAPI reference B2C Commercefor latest reference docs - Web-search
site:developer.salesforce.com SCAPI migration OCAPIfor migration guides - Web-search
Salesforce B2C Commerce OCAPI maintenance mode 2026for deprecation timeline updates - WebFetch:
developer.salesforce.com/docs/commerce/b2c-commerce/guide/b2c-ocapi-overview.html - Confirm OCAPI version support on your instance via Business Manager > Administration > Site Development > Open Commerce API Settings
Conceptual Architecture
Shop API vs Data API
| Aspect | Shop API | Data API |
|---|---|---|
| Purpose | Storefront operations (browse, cart, checkout) | Admin/integration operations (catalog, config, batch) |
| Audience | Shoppers / frontend apps | Admins / ERP / PIM integrations |
| Site scope | Site-specific (/s/{site_id}/dw/shop/) |
Global (/s/-/dw/data/) |
| Auth | Client ID header or customer JWT | JWT bearer token from Account Manager |
| Typical consumers | PWA, mobile apps, kiosks | ERP connectors, OMS, back-office tools |
Authentication Types Overview
| Auth Type | API | Use Case |
|---|---|---|
Client ID header (x-dw-client-id) |
Shop API | Anonymous browsing |
Customer JWT (via /customers/auth) |
Shop API | Registered customer sessions |
| OAuth JWT (Account Manager) | Data API | Server-to-server integrations |
| BM User Grant | Data API | Operations requiring BM user context |
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 · 124 lines · 70 tokens per session scan A c6981f9fddab
sf-b2c-ocapi is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 2d ago), licensed MIT. It adds 70 tokens to every session and 1,438 once invoked, about $0.0003 per session on Opus 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-15.
Other skills, from other repositories
archestra-dev-interactions-migrations
Use BEFORE writing or running any Drizzle migration that touches the interactions table (or any other very large, write-hot table). The interactions table is the platform's biggest, append-heavy table — every LLM proxy call writes a row — so a careless migration can take a write-blocking lock and stall the proxy.…
archestra-dev-llm-providers
Use when adding an LLM provider, changing proxy adapters or provider routes, fixing streaming/tool-call translation bugs, editing model fetchers or model handling, or touching provider credentials/enums and model constants.
archestra-dev-backend
Use when adding or changing Archestra backend routes, models, services, API request/response schemas, endpoint permissions, or OpenAPI/codegen for the generated API client.
debridge
Complete deBridge Protocol SDK for building cross-chain bridges, message passing, and token transfers on Solana. Use when building cross-chain applications, bridging assets between Solana and EVM chains, or implementing trustless external calls.
mppx
TypeScript SDK for the Payment HTTP Authentication Scheme. Handles 402 Payment Required flows with Tempo, Stripe, and other payment methods. Use when integrating payments or mppx into a client or server application.
near-intents
Cross-chain token swap integration using NEAR Intents 1Click API. Use when building swap widgets, bridge interfaces, or multi-chain transfers across EVM, Solana, NEAR, TON, Stellar, and Tron.