Borrowing it
Nothing to install: this file belongs to wfilleman/shopify-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/wfilleman/shopify-mcp-server/main/CLAUDE.mdgit clone --depth 1 https://github.com/wfilleman/shopify-mcp-serverWrote 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/instructions/wfilleman/shopify-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/wfilleman/shopify-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/wfilleman/shopify-mcp-server/claude-md.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.00548 | $0.00548 |
| Opus 5 | $0.00274 | $0.00274 |
| Sonnet 5 | $0.00110 | $0.00110 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
shopify-mcp-server CLAUDE.md 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 7d 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
Shopify MCP Server Development Guidelines
Commands
- Setup:
npm install - Build:
npm run build - Start:
npm start - Dev mode:
npm run dev - Lint:
npm run lint - Type check:
npm run typecheck - Test:
npm test - Single test:
npm test -- -t "test name"
Code Style
- TypeScript: Use strong typing with interfaces/types for all GraphQL responses
- Formatting: Use Prettier with 2-space indentation
- Imports: Group imports (SDK, Shopify, local) with blank line separators
- Naming: camelCase for variables/functions, PascalCase for interfaces/types
- Error Handling: Use try/catch blocks with formatErrorResponse utility
- Documentation: JSDoc comments for public functions with @param and @returns tags
- Structure: Group related GraphQL operations in the same file
- Responses: Always use the formatter utilities from utils/formatters.ts
Shopify API Guidelines
- Use GraphQL for all operations when possible
- Always handle userErrors array in GraphQL responses
- Include ORDER_FRAGMENT for consistent order data retrieval
- Follow the MCP protocol for all tool responses
Shopify GraphQL Mutations
- Format GraphQL mutations with variables as top-level objects:
mutation MyMutation($input: MyInputType!) { operationName(input: $input) { # fields } } - When executing GraphQL, pass variables object with properly structured input:
executeGraphQL<ResponseType>(MUTATION_NAME, { input: { id: "gid://shopify/Resource/123456789", otherField: value } }); - For order operations, always convert order numbers to proper Shopify GraphQL IDs
- Use the following mutation for closing orders (equivalent to archiving):
mutation CloseOrder($input: OrderCloseInput!) { orderClose(input: $input) { order { id closed } userErrors { field message } } }
MCP Server Implementation
- Let the MCP SDK handle core protocol features (initialization, tools listing)
- Keep the server implementation minimal and avoid overriding SDK methods
- Use fallback request handler for custom method handling
- Always provide proper error handling with informative error messages
- Add diagnostic logging for request/response activity
- Test all API endpoints to ensure compatibility with LLM agents
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.
- 7d ago First seen · 70 lines · 548 tokens per session scan A d24c44215fa3
shopify-mcp-server CLAUDE.md is an instructions file published in the GitHub repository wfilleman/shopify-mcp-server (0 stars, last pushed 1y ago), licensed ISC. It adds 548 tokens to every session, about $0.0027 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 instructions, from other repositories
vibetags com-example-service-OrderService.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for orderservice, rules for method calculatetax, rules for method processpayment, rules for method validateorder and context & focus.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).