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 bc-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/bc-performance)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/bc-performance"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/bc-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/bc-performance"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/bc-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.00047 | $0.01282 |
| Opus 5.5 | $0.00019 | $0.00513 |
| Sonnet 5.5 | $0.00009 | $0.00256 |
| Haiku 4.5 | $0.00005 | $0.00128 |
Grade A, and why
bc-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 1mo 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BigCommerce Performance Optimization
Before writing code
Fetch live docs:
- Web-search
site:developer.bigcommerce.com performancefor performance guide - Web-search
bigcommerce stencil theme performance optimizationfor theme tuning - Web-search
bigcommerce core web vitals optimizationfor CWV improvements
Platform-Level Performance
BigCommerce CDN
BigCommerce automatically serves storefronts via its global CDN:
- Static assets (JS, CSS, images) cached at edge
- Akamai-powered infrastructure
- Automatic HTTPS/SSL
- No CDN configuration needed from developers
Server-Side Rendering
Stencil themes are server-rendered by BigCommerce:
- HTML generated on BigCommerce infrastructure
- Response times depend on template complexity and front matter data
- Minimize front matter requests for faster server response
Stencil Theme Optimization
Reduce Front Matter Data
Front matter declares what data to load per page — only request what you need:
- Remove unused front matter sections (e.g.,
related_productsif not displayed) - Reduce
limitvalues to minimum needed - Use
{{#if}}to conditionally render sections, but note the data is still fetched
JavaScript Optimization
- Bundle size: minimize third-party dependencies
- Code splitting: use dynamic imports for page-specific code
- Defer non-critical JS: use
deferorasyncattributes - Remove unused jQuery plugins if the theme ships jQuery
- Tree shaking: ensure webpack is configured for dead code elimination
CSS Optimization
- Remove unused SCSS — audit with coverage tools
- Minimize use of
@extend(causes CSS bloat) - Use CSS custom properties for runtime theming instead of SCSS variables where appropriate
- Critical CSS: inline above-the-fold styles
Image Optimization
- Use BigCommerce's image CDN — images are auto-resized via
{{getImage}}helper - Specify appropriate image dimensions:
{{getImage product.image 'product_size'}} - Use modern formats: BigCommerce CDN serves WebP when supported
- Lazy load below-the-fold images:
loading="lazy" - Use responsive images with
srcsetandsizes
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.
- 1mo ago First seen · 153 lines · 47 tokens per session scan A 315b9591fcf4
bc-performance is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (40 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 1,282 once invoked, about $0.0002 per session on Opus 5.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
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.
magento-module-development
Build custom Magento 2 modules using dependency injection, plugins, observers, and service contracts to extend core functionality cleanly.
magento-indexing-caching
Speed up Magento by managing indexers correctly, configuring Varnish full-page cache, and using Redis for session and object caching.
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.
archestra-dev-testing
Use for test selection and quality across backend, frontend, and e2e; load its backend reference for Vitest projects, mocking, DB fixtures, and performance.
managing-archestra-releases
Runs rolling beta releases, stable patches, and complete stable-line cutovers. Use when backporting fixes, cutting or retiring release branches, configuring release protections, testing artifacts, recovering failed runs, or approving releases.