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/Brahim-Benzarti/Shopify_store-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/brahim-benzarti/shopify_store-mcp/project-context)<a href="https://agentmods.dev/rules/brahim-benzarti/shopify_store-mcp/project-context"><img src="https://agentmods.dev/badge/rules/brahim-benzarti/shopify_store-mcp/project-context.svg" alt="Measured on agentmods" 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.00830 | $0.00830 |
| Opus 5 | $0.00415 | $0.00415 |
| Sonnet 5 | $0.00166 | $0.00166 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
project-context 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 8d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shopify Store MCP Server
Overview
An MCP server that connects to live Shopify stores via Admin and Storefront APIs, enabling AI agents to perform real operations. Unlike documentation-only MCPs, this actually interacts with stores.
Tech Stack
| Component | Technology |
|---|---|
| Runtime | Node.js 18+ with TypeScript (ES2022, ESM) |
| MCP SDK | @modelcontextprotocol/sdk v1.x |
| Admin API | @shopify/admin-api-client |
| Storefront API | @shopify/storefront-api-client |
| Database | SQLite + Prisma |
| Queue | p-queue (rate limiting) |
| Validation | Zod |
| Transport | STDIO |
Project Structure
src/
├── index.ts # Entry point + initialization
├── config.ts # Env loading + validation
├── shopify-client.ts # API client factories
├── errors.ts # Response formatters
├── types.ts # Shared types
├── db.ts # Prisma client singleton
├── queue.ts # Rate-limited queue
├── logger.ts # Operation logging
├── utils/
│ └── polling.ts # Async polling helper
├── graphql/
│ ├── admin/ # Admin API queries
│ │ ├── common/ # Products, orders, customers, etc.
│ │ ├── specialized/ # Inventory, metafields, bulk, files
│ │ └── index.ts # Barrel export
│ └── storefront/ # Storefront API queries
├── tools/ # MCP tools (10 total)
│ ├── shop.ts # get_shop_info
│ ├── graphql.ts # run_graphql_query (universal)
│ ├── smart-*.ts # Smart multi-step tools (5)
│ └── infrastructure.ts # configure, get_history, get_stats
├── prompts/ # MCP prompts (5)
└── resources/ # MCP resources (4)
prisma/
└── schema.prisma # Database schema
Architecture Philosophy
Two-Tier Tool Design
- Generic tools —
run_graphql_queryis the universal escape hatch for ANY Shopify operation - Smart tools — Multi-step workflows that orchestrate multiple API calls
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.
- 8d ago First seen · 100 lines · 830 tokens per session scan A 2b937ea50910
project-context is a cursor rule published in the GitHub repository Brahim-Benzarti/Shopify_store-MCP (3 stars, last pushed 6mo ago), licensed ISC. It adds 830 tokens to every session, about $0.0042 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-08-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.