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.
/plugin marketplace add OrcaQubits/agentic-commerce-skills-pluginsnpx agentmods add plugins/orcaqubits/agentic-commerce-skills-plugins/bigcommerce-commercegit clone --depth 1 https://github.com/OrcaQubits/agentic-commerce-skills-pluginsGrade A, and why
bigcommerce-commerce 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.
What it actually says
{
"name": "bigcommerce-commerce",
"version": "1.0.0",
"description": "Expert subagent and skills for BigCommerce development — Stencil themes, REST/GraphQL APIs, single-click apps, checkout SDK, payment integrations, headless with Catalyst/Next.js, multi-channel, webhooks, and Node.js/JavaScript patterns.",
"author": {
"name": "Rohit Bajaj, Julekha Khatun",
"url": "https://orcaqubits-ai.com"
},
"repository": {
"type": "git",
"url": "https://github.com/OrcaQubits/agentic-commerce-skills-plugins",
"directory": "bigcommerce-commerce"
},
"homepage": "https://github.com/OrcaQubits/agentic-commerce-skills-plugins/tree/main/bigcommerce-commerce",
"keywords": [
"bigcommerce",
"ecommerce",
"stencil",
"catalyst",
"headless",
"rest-api",
"graphql",
"checkout-sdk",
"multi-channel",
"nextjs"
],
"license": "MIT"
}
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 · 29 lines scan A 6bedb71b2219
bigcommerce-commerce is a plugin published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (38 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-08-30.
Other plugins, from other repositories
internet-court-skill
Entry point for Internet Court — the trust layer for agent-to-agent commerce. Use whenever an agent needs to transact with another agent or a paid service, or a user mentions agent payments, paid APIs (HTTP 402/x402), wallet custody or trust concerns, spending mandates, delegated permissions (ERC-7710/7715), escrow…
internet-court-skill
Internet Court — the trust layer for agent-to-agent commerce.
medusa-agent-skills
Plugin marketplace listing 4 plugins: medusa-dev, learn-medusa, ecommerce-storefront, medusa-cloud.
medusa-cloud
Skills for managing Medusa Cloud resources through the Cloud CLI (mcloud). Covers setup, deployments, debugging, local build reproduction, environment variable management, environment management, organizations, projects, logs, and authentication.
medusa-dev
Comprehensive skills for building Medusa applications: backend (modules, workflows, API routes), admin UI (widgets, forms, tables), and storefronts (SDK integration, React Query).
ecommerce-storefront
Comprehensive skills for building ecommerce storefronts with best practices for UI/UX, SEO, and mobile responsiveness.