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.
git clone --depth 1 https://github.com/codeyogi911/shopify-mcpWrote 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/rules/codeyogi911/shopify-mcp/shopify)<a href="https://agentmods.dev/rules/codeyogi911/shopify-mcp/shopify"><img src="https://agentmods.dev/badge/rules/codeyogi911/shopify-mcp/shopify/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/rules/codeyogi911/shopify-mcp/shopify"><img src="https://agentmods.dev/badge/rules/codeyogi911/shopify-mcp/shopify.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.00034 | $0.00034 |
| Opus 5.5 | $0.00014 | $0.00014 |
| Sonnet 5.5 | $0.00007 | $0.00007 |
| Haiku 4.5 | $0.00003 | $0.00003 |
Grade A, and why
shopify 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 1mo 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.
What it actually says
Your rule content
- Always consult shopify dev tools to explore schema and write queries accordingly.
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.
- 1mo ago First seen · 10 lines · 34 tokens per session scan A 3e66fee6ea77
shopify is a cursor rule published in the GitHub repository codeyogi911/shopify-mcp (4 stars, last pushed 1y ago), licensed MIT. It adds 34 tokens to every session, about $0.0001 per session on Opus 5.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-08-31.
Other cursor rules, from other repositories
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
paddle-integration
Conventions for Paddle integration code.
vtex-io-vtex-io-storefront-theme-app
Apply when designing or modifying a VTEX IO storefront theme app — the app that owns store/blocks.json, store/routes.json, store/templates/, store/contentSchemas.json, and the storefront page tree assembled from store.home, store.product, store.search, store.custom, and other native page templates. Covers how a theme…
faststore-faststore-storefront-ref-project-structure-routes-and-config
FastStore project structure, routes, CLI build pipeline, store configuration (discovery.config.js), and naming conventions. Use when understanding how a FastStore project is organized, how the @faststore/cli works, what files to create or modify, how routing works, or how to configure store settings like SEO, API…
medusa
Cursor rule "medusa" from XD3an/awesome-ai-coding-all-in-one, covering medusa rules, general rules, workflow rules, data model rules and service rules.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.