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-performancegit 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-performance)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/sf-performance"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/sf-performance/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-performance"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/sf-performance.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.00056 | $0.01397 |
| Opus 5 | $0.00028 | $0.00698 |
| Sonnet 5 | $0.00011 | $0.00279 |
| Haiku 4.5 | $0.00006 | $0.00140 |
Grade A, and why
sf-performance 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sf-performance
Optimize Salesforce Commerce performance across B2C Commerce (SFCC) and B2B Commerce Cloud platforms.
Before Writing Code
Always fetch live documentation first:
-
B2C Commerce Performance
- Search: "Salesforce B2C Commerce performance optimization 2026"
- Search: "SFCC caching strategies page cache template cache"
- Search: "Salesforce eCDN configuration and cache invalidation"
-
B2B Commerce Performance
- Search: "Lightning Web Components performance optimization 2026"
- WebFetch:
developer.salesforce.com/docs/component-library/documentation/en/lwc/lwc.reference_performance
-
Core Web Vitals
- Search: "Core Web Vitals 2026 targets LCP INP CLS" (INP replaced FID in March 2024)
- WebFetch:
web.dev/vitals/
Conceptual Architecture
Cache Levels (B2C)
| Level | Mechanism | Scope | Use Case |
|---|---|---|---|
| Page Cache | res.cachePeriod / res.cachePeriodUnit |
Full controller response | Product pages, category pages |
| Template Cache | <iscache> ISML tag |
Individual template fragment | Reusable components, static content |
| Object Cache | CacheMgr.getCache() |
Arbitrary data | API responses, computed results |
| CDN Cache | Salesforce eCDN | Static assets + pages | Images, CSS, JS, edge-cached HTML |
Page cache types:
- Public cache: Shared content (product, category pages)
- Private cache: User-specific content (cart, account)
- No cache: Checkout, payment pages
Template cache varyby: Fetch live docs for current supported varyby attribute values -- they are limited and version-specific.
Core Web Vitals Targets
| Metric | Good | Needs Improvement | What It Measures |
|---|---|---|---|
| LCP (Largest Contentful Paint) | < 2.5s | < 4.0s | Main content load time |
| INP (Interaction to Next Paint) | < 200ms | < 500ms | Input responsiveness (replaced FID) |
| CLS (Cumulative Layout Shift) | < 0.1 | < 0.25 | Visual stability |
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 · 131 lines · 56 tokens per session scan A 191daad188cc
sf-performance is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 1,397 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
shopify-theme-optimization
Theme speed and UX optimization — Core Web Vitals, Liquid code, image loading, mobile responsiveness.
shopify
Expert Shopify theme development guidelines for Liquid, Online Store 2.0, CSS, JavaScript, and UX best practices.
shopify-theme-development-guidelines
Expert Shopify theme development with Liquid, Online Store 2.0, and performance best practices.
design-taste-frontend
Use for visual design direction on greenfield, user-facing surfaces — marketing and landing pages, generated apps, portfolio-style or standalone pages. NOT for routine Archestra platform UI work (dashboards, data tables, settings, forms, existing components) — use archestra-dev-frontend for that. Upstream intent…
archestra-dev-frontend
Use when modifying Archestra frontend Next.js/React code, UI components, forms, TanStack Query hooks, generated API client usage, frontend copy, or documentation links.
sfcc-sfra-scss
Best practices for styling and theming SFRA storefronts using SCSS. Use when asked to create style overrides, theming, responsive layouts, or CSS customizations in SFCC.