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-checkoutgit 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-checkout)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/saleor-checkout"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/saleor-checkout/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-checkout"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/saleor-checkout.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.00037 | $0.01915 |
| Opus 5 | $0.00018 | $0.00958 |
| Sonnet 5 | $0.00007 | $0.00383 |
| Haiku 4.5 | $0.00004 | $0.00192 |
Grade A, and why
saleor-checkout 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Saleor Checkout Flow
Before writing code
Fetch live docs:
- Web-search
site:docs.saleor.io checkout flow stepsfor the end-to-end checkout process - Web-search
site:docs.saleor.io checkout mutations graphqlfor checkout creation and update mutations - Web-search
site:docs.saleor.io transaction payment checkoutfor the transaction-based payment flow - Fetch
https://docs.saleor.io/developer/checkout/overviewand review checkout lifecycle and required fields - Web-search
site:docs.saleor.io delivery methods shipping checkoutfor shipping method selection - Fetch
https://docs.saleor.io/developer/payments/overviewand review payment initialization and completion
Checkout Flow Steps
The Saleor checkout follows a sequential flow:
| Step | Mutation | Description |
|---|---|---|
| 1. Create checkout | checkoutCreate |
Initialize checkout with channel and lines |
| 2. Add/update lines | checkoutLinesAdd / checkoutLinesUpdate |
Manage line items in the cart |
| 3. Set email | checkoutEmailUpdate |
Set customer email (for guest checkout) |
| 4. Set shipping address | checkoutShippingAddressUpdate |
Required for physical goods |
| 5. Set billing address | checkoutBillingAddressUpdate |
Required for payment processing |
| 6. Select delivery method | checkoutDeliveryMethodUpdate |
Choose shipping method or warehouse pickup |
| 7. Initialize payment | transactionInitialize |
Start payment with payment App |
| 8. Process payment | transactionProcess |
Handle additional payment steps (3DS, redirects) |
| 9. Complete checkout | checkoutComplete |
Finalize and create the order |
Steps 3-6 can be done in any order, but all must be complete before payment initialization. The checkout validates required fields at each step.
Checkout Creation
Create a checkout by specifying the channel and initial line items:
| Field | Required | Description |
|---|---|---|
channel |
Yes | Channel slug (determines currency, country, available products) |
lines |
Yes | Array of {variantId, quantity} objects |
email |
No | Customer email (can be set later) |
shippingAddress |
No | Shipping address (can be set later) |
billingAddress |
No | Billing address (can be set later) |
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 · 198 lines · 37 tokens per session scan A 6ea3861da5e4
saleor-checkout is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 1,915 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
archestra-dev-interactions-migrations
Use BEFORE writing or running any Drizzle migration that touches the interactions table (or any other very large, write-hot table). The interactions table is the platform's biggest, append-heavy table — every LLM proxy call writes a row — so a careless migration can take a write-blocking lock and stall the proxy.…
archestra-dev-llm-providers
Use when adding an LLM provider, changing proxy adapters or provider routes, fixing streaming/tool-call translation bugs, editing model fetchers or model handling, or touching provider credentials/enums and model constants.
archestra-dev-backend
Use when adding or changing Archestra backend routes, models, services, API request/response schemas, endpoint permissions, or OpenAPI/codegen for the generated API client.
debridge
Complete deBridge Protocol SDK for building cross-chain bridges, message passing, and token transfers on Solana. Use when building cross-chain applications, bridging assets between Solana and EVM chains, or implementing trustless external calls.
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.
near-intents
Cross-chain token swap integration using NEAR Intents 1Click API. Use when building swap widgets, bridge interfaces, or multi-chain transfers across EVM, Solana, NEAR, TON, Stellar, and Tron.