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-widgetsgit 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-widgets)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/bc-widgets"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/bc-widgets/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-widgets"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/bc-widgets.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.00051 | $0.01485 |
| Opus 5.5 | $0.00020 | $0.00594 |
| Sonnet 5.5 | $0.00010 | $0.00297 |
| Haiku 4.5 | $0.00005 | $0.00148 |
Grade A, and why
bc-widgets 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BigCommerce Widgets & Script Manager
Before writing code
Fetch live docs:
- Fetch
https://docs.bigcommerce.com/developer/docs/admin/widgets-and-scripts/overviewfor Widget SDK - Web-search
site:developer.bigcommerce.com scripts apifor Script Manager API - Web-search
bigcommerce page builder widgets customfor custom widget patterns
Widget System
Architecture
Widgets are reusable content components managed via API:
- Widget Template — Handlebars template defining the HTML output
- Widget — an instance of a template with specific configuration data
- Placement — positions a widget in a specific theme region on specific pages
- Page Builder — admin drag-and-drop UI that creates widgets and placements
How It Fits Together
Widget Template (Handlebars + JSON schema)
↓
Widget (template + configuration data)
↓
Placement (widget + region + page)
↓
Rendered on storefront
Widget Templates
Creating a Template
POST /v3/content/widget-templates:
{
"name": "Banner with CTA",
"storefront_api_query": "query { site { settings { storeName } } }",
"schema": [
{
"type": "tab",
"label": "Content",
"sections": [
{
"label": "Banner",
"settings": [
{
"type": "text",
"label": "Heading",
"id": "heading",
"default": "Welcome"
},
{
"type": "text",
"label": "Button Text",
"id": "buttonText",
"default": "Shop Now"
},
{
"type": "text",
"label": "Button URL",
"id": "buttonUrl",
"default": "/shop"
}
]
}
]
}
],
"template": "<div class='banner'><h2>{{heading}}</h2><a href='{{buttonUrl}}'>{{buttonText}}</a></div>"
}
Schema Field Types
| Type | Description |
|---|---|
text |
Text input |
textarea |
Multi-line text |
number |
Numeric input |
boolean |
Toggle/checkbox |
select |
Dropdown select |
color |
Color picker |
imageManager |
Image upload/select |
productId |
Product picker |
categoryId |
Category picker |
range |
Slider |
alignment |
Text alignment |
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 · 218 lines · 51 tokens per session scan A cccce95af6b7
bc-widgets is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (40 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,485 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.
shopify
Expert Shopify theme development guidelines for Liquid, Online Store 2.0, CSS, JavaScript, and UX best practices.
shopify-theme-optimization
Theme speed and UX optimization — Core Web Vitals, Liquid code, image loading, mobile responsiveness.
magento-module-development
Build custom Magento 2 modules using dependency injection, plugins, observers, and service contracts to extend core functionality cleanly.
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.