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 shopify-api-restgit 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/shopify-api-rest)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/shopify-api-rest"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/shopify-api-rest/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/shopify-api-rest"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/shopify-api-rest.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.00060 | $0.00918 |
| Opus 5 | $0.00030 | $0.00459 |
| Sonnet 5 | $0.00012 | $0.00184 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade A, and why
shopify-api-rest 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shopify REST Admin API (DEPRECATED)
DEPRECATION NOTICE: The Shopify REST Admin API was deprecated in October 2024. All new development MUST use the GraphQL Admin API. This skill exists for maintaining legacy code and planning migration.
Before writing code
Fetch live docs:
- Web-search
site:shopify.dev rest admin api deprecationfor deprecation timeline - Web-search
site:shopify.dev migrate rest to graphqlfor migration guide - Fetch
https://shopify.dev/docs/api/admin-restfor REST reference (if maintaining legacy code)
REST API Overview (Legacy)
Endpoints
- Base URL:
https://{store}.myshopify.com/admin/api/{version}/ - Resources:
products.json,orders.json,customers.json, etc. - CRUD via HTTP methods: GET, POST, PUT, DELETE
Authentication
- Header:
X-Shopify-Access-Token: {token} - Same OAuth tokens work for both REST and GraphQL
Rate Limits
- Bucket-based: 40 requests per app per store (leaky bucket)
- Headers:
X-Shopify-Shop-Api-Call-Limit: 32/40 - Plus stores: 80 requests
Pagination
- Cursor-based via
Linkheader (not page numbers) rel="next"andrel="previous"links
REST-to-GraphQL Migration
Common Mappings
| REST Endpoint | GraphQL Equivalent |
|---|---|
GET /products.json |
query { products(first: 50) { edges { node { ... } } } } |
POST /products.json |
mutation { productCreate(input: {...}) { ... } } |
PUT /products/{id}.json |
mutation { productUpdate(input: {...}) { ... } } |
DELETE /products/{id}.json |
mutation { productDelete(input: {id: "..."}) { ... } } |
GET /orders.json |
query { orders(first: 50) { edges { node { ... } } } } |
GET /customers.json |
query { customers(first: 50) { edges { node { ... } } } } |
Key Differences
| Aspect | REST | GraphQL |
|---|---|---|
| Data shape | Fixed response | Client-defined |
| Rate limiting | Request count (40/s) | Cost-based (1000 points) |
| Pagination | Link headers | Cursor arguments |
| Bulk operations | Not available | bulkOperationRunQuery |
| Webhooks | REST endpoint | Same (subscription via GraphQL) |
| ID format | Numeric (12345) |
GID (gid://shopify/Product/12345) |
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 · 91 lines · 60 tokens per session scan A 2df9caefc3ce
shopify-api-rest is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 2d ago), licensed MIT. It adds 60 tokens to every session and 918 once invoked, about $0.0003 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.