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-paymentsgit 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-payments)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/saleor-payments"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/saleor-payments/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-payments"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/saleor-payments.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.00038 | $0.01899 |
| Opus 5 | $0.00019 | $0.00949 |
| Sonnet 5 | $0.00008 | $0.00380 |
| Haiku 4.5 | $0.00004 | $0.00190 |
Grade A, and why
saleor-payments 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 3d 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 Payment Processing
Before writing code
Fetch live docs:
- Web-search
site:docs.saleor.io transaction payment flowfor the transaction-based payment model - Web-search
site:docs.saleor.io payment app sync webhooksfor payment App implementation patterns - Web-search
site:docs.saleor.io transaction events CHARGE_REQUESTEDfor transaction event types - Fetch
https://docs.saleor.io/developer/payments/overviewand review the full payment lifecycle - Web-search
site:docs.saleor.io refund transactionRequestActionfor refund processing flow - Fetch
https://docs.saleor.io/developer/app-store/apps/stripe/overviewand review Stripe App integration patterns
Transaction Payment Flow
Saleor uses a transaction-based payment model (replacing the legacy Payment model):
| Step | Component | Description |
|---|---|---|
| 1. List gateways | checkout.availablePaymentGateways |
Query available payment Apps for the checkout |
| 2. Initialize session | transactionInitialize |
Send payment request to the payment App |
| 3. Process (if needed) | transactionProcess |
Handle additional steps (3DS, redirect) |
| 4. Transaction events | Automatic | Payment App reports events via webhooks |
| 5. Complete checkout | checkoutComplete |
Finalize order after successful payment |
The transaction flow is designed for asynchronous payment processing. The payment App controls the actual charge timing and reports results back via transaction events.
Transaction Events
Transaction events track the lifecycle of a payment:
Request Events (Saleor to Payment App)
| Event Type | Description |
|---|---|
AUTHORIZATION_REQUEST |
Request to authorize (hold) funds |
CHARGE_REQUEST |
Request to capture payment |
REFUND_REQUEST |
Request to refund payment |
CANCEL_REQUEST |
Request to void/cancel authorization |
Success Events (Payment App to Saleor)
| Event Type | Description |
|---|---|
AUTHORIZATION_SUCCESS |
Funds successfully authorized |
CHARGE_SUCCESS |
Payment successfully captured |
REFUND_SUCCESS |
Refund successfully processed |
CANCEL_SUCCESS |
Authorization successfully cancelled |
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.
- 3d ago First seen · 198 lines · 38 tokens per session scan A 7370619b53aa
saleor-payments is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 3d ago), licensed MIT. It adds 38 tokens to every session and 1,899 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
sales-ledger
Provides the Q3 sales ledger workbook for reporting tasks. Use when a task asks you to compute bonuses or totals over the sales ledger; the data lives only in this skill's bundled workbook.
internet-court
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…
okx-agent-payments-protocol
Use when an agent hits HTTP 402 / payment-required, or the user mentions x402, x402Version, X-PAYMENT, PAYMENT-REQUIRED, PAYMENT-SIGNATURE, WWW-Authenticate: Payment, permit2, upto, metered billing, a payment channel / voucher / session, channelId / channelid, opening / closing / topping up / settling / refunding a…
jupiter-lend
Interact with Jupiter Lend Protocol. Read-only SDK (@jup-ag/lend-read) for querying liquidity pools, lending markets (jlTokens), and vaults. Write SDK (@jup-ag/lend) for lending (deposit/withdraw) and vault operations (deposit collateral, borrow, repay, manage positions).
okx-dapp-discovery
Plugin router for 20 third-party DeFi protocols (Polymarket, Aave, Hyperliquid, PancakeSwap, Morpho, Raydium, Curve, Compound, Pendle, Lido, ether.fi, GMX, Kamino, Orca, Meteora, Clanker, pump.fun, Uniswap) and their protocol-native tokens (HYPE, HLP, eETH, weETH, stETH, wstETH, LDO, GHO, CAKE, CRV, COMP, RAY, ETHFI…
lifi
LI.FI REST API for cross-chain and same-chain token swaps, bridging, DeFi deposits (Composer), yield discovery (Earn), and intent-based execution (Intents). USE THIS SKILL WHEN USER WANTS TO: Swap tokens between different blockchains (e.g., "swap USDC on Ethereum to ETH on Arbitrum") Bridge tokens to another chain…