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/commercetools/commerce-mcp/refactor-functionsgit clone --depth 1 https://github.com/commercetools/commerce-mcpWhat 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.00014 | $0.01237 |
| Opus 5 | $0.00007 | $0.00619 |
| Sonnet 5 | $0.00003 | $0.00247 |
| Haiku 4.5 | $0.00001 | $0.00124 |
Grade A, and why
refactor-functions 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.
This is a copy
94% identical to refactor-functions — 158 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactoring a tool Function in @commercetools/commerce-agent
This document outlines the steps taken to refactor a function in @commercetools/commerce-agent to connect to commercetools API.
The following steps are defining implementation of an example cart.read. So the (namespace) here refers to cart.
NOTES:
1. CRUD functions are read, update and create. do not add delete functions.
2. DO NOT MODIFY `parameters.ts` or `prompts.ts` or `tools.ts`
3. when creating update base functions, use get (by id or key) base functions to first fetch the entity, and use the version from the fetched entity in the update payload
Refactor steps
-
Create a
base.functions.tsfile in thenamespacedirectory. This file will export a couple of basic CRUD functions that will be used inside other files in this namespace. you can extract this base functions from currentfunctions.tsfile in the namespace.- IMPORTANT: base functions should be generic as possible, e.g. instead of having a separate function for query cart for a specific user and another one for user in a store, we create one that accepts a "where" cluase.
- Note: sometimes the commercetools SDK has different endpoint when a parameter is present, like query in store (look to the code sample below). in that case, we check that parameter inside the base function but keep the function as simple as possible and low complexity.
- GOAL: the goal of this step is maximize reusability.
- example: base functions created for 'cart.read' are: readCartById, readCartByKey, queryCart, queryCarts.
- file example:
typescript/src/shared/cart/base.functions.ts - code sample:
const queryCart = async ( apiRoot: ApiRoot, projectKey: string, queryArgs: any, storeKey?: string ) => { if (storeKey) { const carts = await apiRoot .withProjectKey({ projectKey }) .inStoreKeyWithStoreKeyValue({ storeKey }) .carts() .get({ queryArgs }) .execute(); return carts.body; } const carts = await apiRoot .withProjectKey({ projectKey }) .carts() .get({ queryArgs }) .execute(); return carts.body; };
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 · 115 lines · 14 tokens per session scan A 2ba5c3018293
refactor-functions is a cursor rule published in the GitHub repository commercetools/commerce-mcp (4 stars, last pushed 21d ago), licensed MIT. It adds 14 tokens to every session and 1,237 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to refactor-functions, differing in 158 lines, and is treated as a copy.
Other cursor rules, from other repositories
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
pro-deck-builder
Create polished HTML slide decks and PDF-ready documents for consulting deliverables. Uses the RRBC design system with warm light mode, dark mode cover pages, Lora/Inter/Roboto Mono typography, and data visualization palette. Trigger on 'deck', 'slides', 'presentation', 'pitch deck', 'keynote', 'report', or 'PDF'.
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
facebook-ads
Meta Ads (Facebook & Instagram) platform expertise. Audit campaigns, audiences, creative strategy, pixel tracking, and CAPI. Use when the user asks about Facebook Ads, Instagram Ads, Meta Ads, social media advertising, Advantage+ campaigns, or Meta pixel/CAPI setup.
paddle-integration
Conventions for Paddle integration code.
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…