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-testinggit 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-testing)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/saleor-testing"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/saleor-testing/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-testing"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/saleor-testing.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.00042 | $0.01983 |
| Opus 5 | $0.00021 | $0.00992 |
| Sonnet 5 | $0.00008 | $0.00397 |
| Haiku 4.5 | $0.00004 | $0.00198 |
Grade A, and why
saleor-testing 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Saleor Testing
Before writing code
Fetch live docs:
- Web-search
site:github.com/saleor/saleor pytest conftest fixturesfor Saleor's test setup and existing fixtures - Web-search
site:docs.saleor.io app testing webhooksfor App testing patterns and webhook verification - Web-search
site:docs.saleor.io graphql API testingfor GraphQL query and mutation testing approaches - Fetch
https://github.com/saleor/saleor/blob/main/conftest.pyand review root-level test configuration - Web-search
site:docs.pytest.org fixtures factory_boy djangofor pytest fixtures and factory_boy integration
Test Architecture
Saleor follows a layered testing approach:
| Layer | Tool | Purpose |
|---|---|---|
| Unit tests | pytest | Test individual functions, utilities, and model methods |
| Integration tests | Django test client | Test GraphQL API endpoints with database |
| App tests | pytest + httpx/requests-mock | Test App webhooks, signature verification |
| E2E tests | pytest + API client | Test full user flows through the API |
Pytest Setup
Core Configuration
| File | Purpose |
|---|---|
pytest.ini / pyproject.toml |
Pytest settings, markers, default flags |
conftest.py (root) |
Shared fixtures, database setup, API clients |
conftest.py (per-app) |
App-specific fixtures and helpers |
Essential pytest Settings
| Setting | Value | Purpose |
|---|---|---|
DJANGO_SETTINGS_MODULE |
saleor.tests.settings |
Test-specific Django settings |
--reuse-db |
Flag | Reuse test database across runs for speed |
--no-migrations |
Flag | Skip migrations; create tables directly |
-x |
Flag | Stop on first failure during development |
-n auto |
Flag | Parallel execution with pytest-xdist |
Key pytest Plugins
| Plugin | Purpose |
|---|---|
pytest-django |
Django integration, database access, settings override |
pytest-xdist |
Parallel test execution |
pytest-mock |
Mock and patch utilities |
pytest-asyncio |
Async test support |
pytest-vcr |
Record and replay HTTP interactions |
pytest-factoryboy |
factory_boy integration with pytest fixtures |
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 · 197 lines · 42 tokens per session scan A 2711527d3eb5
saleor-testing is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 1,983 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-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.
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-e2e
Use when writing, debugging, or running Archestra Playwright e2e tests, API/UI fixtures, WireMock-backed tests, local/CI e2e setup, or test selectors.
harn-testing
Test owning interfaces, canonical paths, liveness, replay, and stochastic quality at the right altitude.
testing-patterns
Testing strategy: pyramid, AAA, mocks/fakes/stubs, flaky tests, coverage. Triggers: test, fixture, mock, stub, e2e, TDD, Playwright, Cypress, flaky, coverage, property-based.
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.