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-ordersgit 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-orders)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/saleor-orders"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/saleor-orders/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-orders"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/saleor-orders.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.00036 | $0.01840 |
| Opus 5 | $0.00018 | $0.00920 |
| Sonnet 5 | $0.00007 | $0.00368 |
| Haiku 4.5 | $0.00004 | $0.00184 |
Grade A, and why
saleor-orders 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Saleor Order Management
Before writing code
Fetch live docs:
- Web-search
site:docs.saleor.io orders order lifecycle statusfor order model and state transitions - Web-search
site:docs.saleor.io fulfillments order fulfillmentfor fulfillment creation and tracking - Web-search
site:docs.saleor.io returns refunds orderfor return and refund workflows - Fetch
https://docs.saleor.io/developer/order/overviewand review order statuses, events, and mutations - Web-search
site:docs.saleor.io draft ordersfor draft order creation and completion patterns - Fetch
https://docs.saleor.io/developer/order/order-fulfillmentand review fulfillment line items and tracking
Order Status and States
Order Status
| Status | Description |
|---|---|
UNCONFIRMED |
Order created but not yet confirmed (e.g., pending payment) |
UNFULFILLED |
Order confirmed and paid; no items shipped yet |
PARTIALLY_FULFILLED |
Some items have been shipped |
FULFILLED |
All items have been shipped |
PARTIALLY_RETURNED |
Some items have been returned |
RETURNED |
All items have been returned |
CANCELED |
Order has been cancelled |
Authorization Status
| Status | Description |
|---|---|
NONE |
No payment authorized |
PARTIAL |
Partial amount authorized |
FULL |
Full amount authorized |
Charge Status
| Status | Description |
|---|---|
NONE |
No payment charged |
PARTIAL |
Partial amount charged |
FULL |
Full amount charged |
OVERCHARGED |
Charged amount exceeds order total |
Order Creation Flow
Orders in Saleor are typically created through the checkout completion process:
| Step | Description |
|---|---|
| 1. Checkout completed | Customer completes checkout with payment |
| 2. Order created | System generates order with status UNCONFIRMED or UNFULFILLED |
| 3. Payment confirmed | Transaction events confirm successful charge |
| 4. Ready for fulfillment | Order moves to UNFULFILLED status |
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 · 200 lines · 36 tokens per session scan A 08d4dc6c64fb
saleor-orders is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 1,840 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
openserv-ideaboard-api
Quick-start guide and API overview for the OpenServ Ideaboard - a platform where AI agents can submit ideas, pick up work, collaborate with multiple agents, and deliver x402 payable services. Use when interacting with the Ideaboard or building agents that find and ship ideas. Read reference.md for the full API…
openserv-multi-agent-workflows
Multi-agent workflow examples to work together on the OpenServ Platform. Covers agent discovery, multi-agent workspaces, task dependencies, and workflow orchestration using the Platform Client. Read reference.md for the full API reference. Read openserv-agent-sdk and openserv-client for building and running agents.
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.
arwp-braidgraph
Trace why a website change exists, connect repository transformations back to evidence and rules, identify missing verification or outcome evidence, and compute source/rule change blast radius through the canonical ARWP BraidGraph instead of inventing a parallel provenance model. Use for change explanation…
arwp-portfolio-fleet
Inspect and verify multiple local website repositories and their public ARWP profiles from one versioned workspace manifest. Use for portfolio-wide status, drift triage, repeated local checks, bounded live checks, or choosing the next site to improve. Do not use for a single-site implementation or as authorization to…
arwp-repository-stewardship
Audit, simplify, map and maintain a website repository so humans and coding agents can understand it quickly, remove proven dead weight safely, preserve source-of-truth and evidence boundaries, and install lightweight navigation and drift checks without treating file-count reduction as a quality goal.