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-setupgit 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-setup)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/sf-setup"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/sf-setup/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-setup"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/sf-setup.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.00069 | $0.01543 |
| Opus 5 | $0.00034 | $0.00772 |
| Sonnet 5 | $0.00014 | $0.00309 |
| Haiku 4.5 | $0.00007 | $0.00154 |
Grade A, and why
sf-setup 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Salesforce Commerce Development Setup
Before Writing Code
Fetch live docs before setting up a project.
- Web-fetch:
https://github.com/SalesforceCommerceCloud/sfcc-cifor sfcc-ci CLI commands - Web-search: "site:developer.salesforce.com sf cli getting started 2026" for sf CLI setup
- Web-search: "site:developer.salesforce.com SFRA getting started 2026" for SFRA project setup
- Web-fetch:
https://developer.salesforce.com/docs/commerce/b2c-commerce/guide/api-doc.htmlfor SFRA reference - Web-search: "site:developer.salesforce.com commerce cloud b2c b2b documentation 2026"
Conceptual Architecture
Prerequisites
B2C Commerce (SFCC) requires:
- Business Manager account (provided by Salesforce or your org)
- Sandbox instance (e.g.,
dev01-realm-customer.demandware.net) - API client credentials (client ID + secret) for sfcc-ci authentication
- Account Manager credentials for WebDAV/OCAPI
B2B Commerce (Lightning) requires:
- Salesforce org (Developer Edition, sandbox, or production) with B2B Commerce license
- sf CLI installed (
npm install -g @salesforce/cli) - Scratch org or sandbox for isolated development
CLI Tools
| Tool | Platform | Install | Auth |
|---|---|---|---|
| sfcc-ci | B2C | npm install -g sfcc-ci |
sfcc-ci client:auth (client ID + secret) |
| sf CLI | B2B | npm install -g @salesforce/cli |
sf org login web or sf org login jwt |
Key sfcc-ci Commands:
sfcc-ci code:deploy-- upload code to sandboxsfcc-ci code:activate-- activate a code versionsfcc-ci sandbox:create/sandbox:list-- manage on-demand sandboxessfcc-ci job:run-- execute Business Manager jobs
Key sf CLI Commands:
sf project deploy start-- deploy metadata to orgsf org create scratch-- create scratch orgsf apex run test-- run Apex testssf data import tree-- import sample data
Project Structures
B2C SFRA Cartridge Project:
sfra-project/
cartridges/
app_storefront_base/ # Base (never modify)
app_custom_storefront/ # Custom overlay
cartridge/
controllers/, models/, scripts/
templates/, client/ (js, scss)
dw.json, package.json, webpack.config.js
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 · 166 lines · 69 tokens per session scan A b6dc8635dc0e
sf-setup is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 2d ago), licensed MIT. It adds 69 tokens to every session and 1,543 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-investigate
Use when investigating Archestra bugs or incidents — staging issues, backend 50x errors, Drizzle failed queries, DB connection pressure, deploy regressions, or Kubernetes/runtime symptoms. Orientation only; defers the process to /investigate.
0g-compute
0G Compute Network guide for decentralized AI inference, fine-tuning, and GPU services. Covers chatbots, image generation, speech-to-text, SDK integration (0g-serving-broker), processResponse API, broker.inference methods, CLI commands (0g-compute-cli), and account management. Use this skill for any 0G compute, 0G AI…
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.
cloud-claw-launch-agent
Use this skill when the user wants to launch a new AltClaw, OpenClaw, PicoClaw, or Ottie deployment through Cloud Claw. Covers the same user-facing fields and constraints exposed in the Cloud Claw UI, using the local altllm cloud-claw- commands. Do NOT use for post-launch lifecycle tasks like start/stop/delete/logs…
cloud-claw
Use this umbrella skill when the request spans multiple Cloud Claw user-facing domains, especially launching a new AltClaw or OpenClaw VM and then managing lifecycle, logs, renewal, or dashboard access through the local altllm cloud-claw- commands in this repository.
mcloud-logs
Execute mcloud logs to fetch and stream runtime logs for Cloud environments. Use when reading backend or storefront logs, filtering by time range, searching for errors, or scoping logs to a specific deployment.