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-setupgit 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-setup)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/saleor-setup"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/saleor-setup/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-setup"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/saleor-setup.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.01505 |
| Opus 5 | $0.00023 | $0.00753 |
| Sonnet 5 | $0.00009 | $0.00301 |
| Haiku 4.5 | $0.00005 | $0.00151 |
Grade A, and why
saleor-setup 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Saleor Development Setup
Before writing code
Fetch live docs:
- Fetch
https://docs.saleor.io/setup/architecturefor architecture overview - Web-search
site:docs.saleor.io saleor-platform docker compose setupfor Docker-based quickstart - Web-search
site:docs.saleor.io saleor CLI installationfor CLI tooling and commands - Web-search
site:docs.saleor.io environment variables configurationfor .env reference - Web-search
site:github.com saleor/saleor-platform docker-composefor latest Compose file
Prerequisites
Required Software
| Software | Minimum Version | Purpose |
|---|---|---|
| Python | 3.12+ | Saleor core runtime |
| PostgreSQL | 14+ | Primary database |
| Redis | 6+ | Celery broker, caching |
| Node.js | 18+ | Dashboard and storefront apps |
| Docker & Docker Compose | latest | Recommended local environment |
| Git | any | Version control |
PostgreSQL Setup (Without Docker)
- Create a dedicated database:
CREATE DATABASE saleor; - Create a user with full privileges on that database
- Connection string format:
postgres://user:password@localhost:5432/saleor
Redis Setup
- Default connection:
redis://localhost:6379 - Required for Celery task queue and caching layer
- Saleor does not fall back to an in-memory broker -- Redis is mandatory
Docker Compose Quickstart (saleor-platform)
The saleor-platform repository bundles all Saleor services into a single Compose stack:
| Service | Container | Port |
|---|---|---|
| Saleor Core (API) | saleor-api |
8000 |
| Saleor Dashboard | saleor-dashboard |
9000 |
| Saleor Storefront | saleor-storefront |
3000 |
| PostgreSQL | saleor-db |
5432 |
| Redis | saleor-redis |
6379 |
| Celery Worker | saleor-worker |
-- |
| Jaeger (tracing) | jaeger |
16686 |
| Mailpit (email) | mailpit |
8025 |
Clone the platform repository and start all services with docker compose up.
Saleor CLI
| Command | Purpose |
|---|---|
saleor login |
Authenticate with Saleor Cloud |
saleor env list |
List available environments |
saleor env create |
Create a new Cloud environment |
saleor tunnel |
Expose local app to Saleor for webhook delivery |
saleor app create |
Scaffold a new Saleor App |
saleor app tunnel |
Tunnel local app for development |
saleor storefront create |
Scaffold a storefront project |
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 · 148 lines · 46 tokens per session scan A a361c33113d0
saleor-setup 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,505 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-investigate
Use when investigating Archestra bugs or incidents — staging issues, backend 50x errors, Drizzle failed queries, DB connection pressure, deploy regressions, or Kubernetes/runtime symptoms. Orientation only; defers the process to /investigate.
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.
ak-cloud-deploy
Deploy an Agent Kernel project to AWS, Azure, or GCP using Terraform modules, or to any Kubernetes cluster (on-prem, baremetal, EKS) using the official Helm chart. Supports serverless and containerized modes for all three clouds. AWS supports execution modes (restsync, restasync, async, stream), queue-based scalable…
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.