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 agentmods add rules/brahim-benzarti/shopify_store-mcp/adding-toolsgit 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/adding-tools)<a href="https://agentmods.dev/rules/brahim-benzarti/shopify_store-mcp/adding-tools"><img src="https://agentmods.dev/badge/rules/brahim-benzarti/shopify_store-mcp/adding-tools.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 | $0.00000 | $0.01181 |
| Opus 5 | $0.00000 | $0.00590 |
| Sonnet 5 | $0.00000 | $0.00236 |
| Haiku 4.5 | $0.00000 | $0.00118 |
Grade A, and why
adding-tools 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 4d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adding New Tools
Decision: Smart Tool vs GraphQL Query?
Use run_graphql_query when:
- Single API call
- Standard CRUD operation
- Agent can handle the response
Create a Smart Tool when:
- Multiple API calls needed
- Polling/async operations
- Complex orchestration
- Response needs transformation
Creating a Smart Tool
1. Create the tool file
// src/tools/smart-example.ts
import { z } from "zod";
import type { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import type { AdminApiClient } from "../shopify-client.js";
import {
formatSuccessResponse,
formatErrorResponse,
formatGraphQLErrors,
} from "../errors.js";
import { enqueue } from "../queue.js";
import { logOperation } from "../logger.js";
export function registerSmartExampleTools(
server: McpServer,
client: AdminApiClient,
storeDomain: string
): void {
server.registerTool(
"smart_example",
{
title: "Smart Example Tool",
description:
"Describe what this tool does, when to use it, and what it returns. " +
"Be specific about the workflow it handles.",
inputSchema: {
requiredParam: z.string().describe("What this parameter does"),
optionalParam: z.number().optional().describe("Optional parameter"),
},
annotations: {
readOnlyHint: false,
destructiveHint: false,
idempotentHint: true,
openWorldHint: false,
},
},
async ({ requiredParam, optionalParam }) => {
const startTime = Date.now();
try {
// Step 1: First API call
const step1 = await enqueue(() =>
client.request(QUERY_1, { variables: { requiredParam } })
);
if (step1.errors) {
return formatGraphQLErrors(step1);
}
// Step 2: Process and make second call
const step2 = await enqueue(() =>
client.request(QUERY_2, { variables: { id: step1.data.id } })
);
// Log the operation
await logOperation({
storeDomain,
toolName: "smart_example",
operationType: "mutation",
query: "smart_example workflow",
variables: { requiredParam, optionalParam },
response: step2.data,
success: true,
durationMs: Date.now() - startTime,
});
return formatSuccessResponse({
result: step2.data,
stepsCompleted: 2,
});
} catch (error) {
return formatErrorResponse(error);
}
}
);
}
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.
- 4d ago First seen · 199 lines · 0 tokens per session scan A 3ae02d9f682a
adding-tools is a cursor rule published in the GitHub repository Brahim-Benzarti/Shopify_store-MCP (3 stars, last pushed 6mo ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 1,181 tokens. 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
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.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.