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 medusa-securitygit 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/medusa-security)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/medusa-security"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/medusa-security/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/medusa-security"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/medusa-security.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.00046 | $0.01568 |
| Opus 5 | $0.00023 | $0.00784 |
| Sonnet 5 | $0.00009 | $0.00314 |
| Haiku 4.5 | $0.00005 | $0.00157 |
Grade A, and why
medusa-security 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Medusa v2 Security
Before writing code
Fetch live docs:
- Web-search
site:docs.medusajs.com authenticationfor auth strategies and API key setup - Web-search
site:docs.medusajs.com api key publishable secretfor API key types - Web-search
site:docs.medusajs.com CORS configurationfor cross-origin resource sharing - Fetch
https://docs.medusajs.com/learn/fundamentals/api-routes/middlewaresfor middleware and auth config - Web-search
site:docs.medusajs.com medusa-config auth providersfor auth provider registration
Authentication Architecture
Admin vs Store Authentication
Medusa v2 separates admin and storefront authentication into distinct flows:
| Aspect | Admin Auth | Store Auth |
|---|---|---|
| Actor type | user |
customer |
| API scope | /admin/* routes |
/store/* routes |
| Default provider | emailpass |
emailpass |
| Session cookie | Admin session cookie | Store session cookie |
| API key support | Secret API key (Bearer) | Publishable API key (header) |
| JWT usage | Admin JWT token | Customer JWT token |
| Middleware | authenticate("user", ...) |
authenticate("customer", ...) |
Auth Provider System
Auth Module
├── emailpass — email + password (default)
├── google — OAuth 2.0 via Google
├── github — OAuth 2.0 via GitHub
└── custom — implement AbstractAuthModuleProvider
Auth providers are registered in medusa-config.ts under the auth module configuration. Each provider handles a specific identity verification strategy.
API Key Types
| Key Type | Header | Purpose | Visibility |
|---|---|---|---|
| Publishable | x-publishable-api-key |
Storefront API access, scopes to sales channels | Safe for client-side |
| Secret | Authorization: Bearer <key> |
Admin API access, full permissions | Server-side only |
- Publishable keys are created in the admin dashboard and tied to sales channels
- Secret keys grant admin-level access and must never be exposed to browsers
- Store API routes require a publishable key header for sales channel scoping
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 · 169 lines · 46 tokens per session scan A d7e5214e2baa
medusa-security is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 1,568 once invoked, about $0.0002 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
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.
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.
archestra-dev-testing
Use when deciding whether a change needs a test and at which level — unit, backend route-level integration, MSW-backed frontend integration, or e2e — or when reviewing tests for the "fluff test" anti-pattern. Start here before archestra-dev-backend-tests or archestra-dev-e2e.
migrate-to-archestra
Migrate an existing agentic PoC/pilot (Claude Code project files, MCP configs, hooks, local tools, openclaw config, or similar hand-rolled setup artifacts) into an Archestra instance. Use when the user wants to move, port, or convert an existing agentic setup into an Archestra pilot.
archestra-dev-backend-tests
Use when writing or modifying Archestra backend unit tests (platform/backend/src//.test.ts) — mocking modules, stubbing globals, database fixtures, vitest projects/isolation, or test performance.
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.