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-controllersgit 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-controllers)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/sf-b2c-controllers"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/sf-b2c-controllers/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-controllers"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/sf-b2c-controllers.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.00055 | $0.01395 |
| Opus 5 | $0.00028 | $0.00698 |
| Sonnet 5 | $0.00011 | $0.00279 |
| Haiku 4.5 | $0.00006 | $0.00139 |
Grade A, and why
sf-b2c-controllers 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sf-b2c-controllers
Build SFRA controllers for request handling in Salesforce B2C Commerce Cloud.
Before Writing Code
Fetch live documentation FIRST:
-
Web-search for:
- "Salesforce B2C Commerce SFRA controllers documentation 2026"
- "SFCC server module middleware patterns"
- "B2C Commerce controller CSRF protection best practices"
-
Web-fetch official sources:
github.com/SalesforceCommerceCloud/storefront-reference-architecture(SFRA controllers)- Salesforce B2C Commerce server module API reference
-
Verify before coding: current server module syntax, middleware chain methods, CSRF validation requirements, form validation patterns in latest SFRA.
Conceptual Architecture
Controller Basics
Controllers are route handlers defined using the server module. Routes follow the naming convention ControllerName-ActionName (e.g., Product-Show, Cart-AddProduct).
- Controller file:
controllers/Product.js - Route:
Product-Show - URL:
https://site.com/Product-Show?pid=12345
Every controller file ends with module.exports = server.exports();
Server Module Methods
| Method | HTTP | Purpose | Example |
|---|---|---|---|
server.get(name, ...mw, handler) |
GET | Display pages | Product-Show, Cart-Show |
server.post(name, ...mw, handler) |
POST | Form submissions | Cart-AddProduct, Account-Register |
server.use(name, ...mw, handler) |
Any | Shared logic, API endpoints | Method-agnostic handlers |
Middleware Chain
Middleware functions execute left to right before the final handler. Each must call next() to continue the chain.
server.post('Action',
server.middleware.https, -> 1. Force HTTPS
csrfProtection.validateRequest, -> 2. Validate CSRF
userLoggedIn.validateLoggedIn, -> 3. Require login
function (req, res, next) {} -> 4. Handler
);
Common built-in middleware:
server.middleware.https-- force HTTPScsrfProtection.validateRequest-- CSRF token validationcsrfProtection.generateToken-- generate CSRF token for formsuserLoggedIn.validateLoggedIn-- require authenticated userconsentTracking.consent-- consent tracking check
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 · 150 lines · 55 tokens per session scan A 03721b967d02
sf-b2c-controllers is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 1,395 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.
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.
arwp-agent-discovery
Add or repair machine-readable agent discovery and interoperability surfaces for a website. Use when asked to expose llms.txt, AGENTS.md, Agent Skills, ARD, MCP, A2A, WebMCP, OpenAPI, API catalogs, agent-readable sitemaps, or an ARWP site profile. Discover what the site truly supports, prefer upstream standards, and…