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/updated-new-functiongit 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.02379 |
| Opus 5 | $0.00007 | $0.01189 |
| Sonnet 5 | $0.00003 | $0.00476 |
| Haiku 4.5 | $0.00001 | $0.00238 |
Grade A, and why
updated-new-function 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 yesterday.
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
88% identical to updated-new-function — 287 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating a New namespace tool Function in @commercetools/commerce-agent
This document outlines the steps taken to implement a new function in @commercetools/commerce-agent to connect to commercetools API.
The following steps are defining implementation of an example products.create. So the (namespace) here refers to product.
Implementation Steps
- Gather info regarding the (namespace)
- Search commercetools docs at https://docs.commercetools.com/api and find the (namespace)
- In this example
https://docs.commercetools.com/api/projects/productsand ProductDraft
-
Define Parameter Schema
- Using the namespace fetched in previous step , Created
createProductParametersintypescript/src/shared/(namespace)/parameters.ts - Used Zod for type validation
- Included all required and optional fields from ProductDraft
- Created a separate
productVariantDraftschema for reusability
- Using the namespace fetched in previous step , Created
-
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" clause.
- 3.1: 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.
- 3.2: No delete operation.
- 3.3: in the base update, call the base get function to fetch the version from the entity and use it in the update call.
- 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.tsIMPORTANT: functions.ts usually exports 3 functions: read, create and update. If there are more ways to read the entity (by id or key or query), embed all in one "read" exported function and adjust the parameters and prompts as well.
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.
- yesterday First seen · 227 lines · 14 tokens per session scan A f4ecea78702c
updated-new-function 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 2,379 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to updated-new-function, differing in 287 lines, and is treated as a copy.
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.