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 saleor-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/saleor-security)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/saleor-security"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/saleor-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/saleor-security"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/saleor-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.00039 | $0.02022 |
| Opus 5 | $0.00019 | $0.01011 |
| Sonnet 5 | $0.00008 | $0.00404 |
| Haiku 4.5 | $0.00004 | $0.00202 |
Grade A, and why
saleor-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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Saleor Security
Before writing code
Fetch live docs:
- Web-search
site:docs.saleor.io authentication JWT tokensfor current JWT authentication flow - Web-search
site:docs.saleor.io apps permissionsfor App token authentication and permission model - Web-search
site:docs.saleor.io OIDC OpenID Connectfor OIDC integration configuration - Web-search
saleor webhook payload signature JWS verificationfor webhook signature verification - Fetch
https://docs.saleor.io/developer/app-store/overviewfor App authentication patterns - Web-search
saleor CORS security headers productionfor CORS and header configuration
JWT Authentication Flow
Saleor uses JSON Web Tokens for staff and customer authentication. Tokens are obtained via GraphQL mutations and passed as Bearer tokens.
Token Lifecycle
| Operation | GraphQL Mutation | Token Type | Expiry |
|---|---|---|---|
| Customer login | tokenCreate |
Access + Refresh | Access: 5 min, Refresh: 30 days |
| Staff login | tokenCreate |
Access + Refresh | Access: 5 min, Refresh: 30 days |
| Refresh | tokenRefresh |
New access token | 5 min (configurable) |
| Verify | tokenVerify |
Validity check | N/A |
| Deactivate | tokensDeactivateAll |
Invalidate all | N/A |
Token Usage
- Pass the access token in the
Authorization: Bearer <token>header - Refresh tokens are used only to obtain new access tokens
- Access tokens are short-lived by design to limit exposure
- CSRF token is required for cookie-based authentication (Dashboard)
OIDC Integration
Saleor supports OpenID Connect for federated authentication. Saleor acts as an OAuth client, delegating login to an external identity provider.
OIDC Configuration Modes
| Mode | Description | Use Case |
|---|---|---|
| Saleor as OAuth client | Delegates login to external IdP | SSO with corporate directory |
| Authorization Code flow | Standard OIDC flow with code exchange | Web applications |
| ID token login | Accept ID token from external IdP | Mobile or SPA apps |
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 · 186 lines · 39 tokens per session scan A e05bc9632533
saleor-security is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 2,022 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.