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/mcp-essentials/updated-new-functiongit clone --depth 1 https://github.com/commercetools/mcp-essentialsWhat 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.00016 | $0.02404 |
| Opus 5 | $0.00008 | $0.01202 |
| Sonnet 5 | $0.00003 | $0.00481 |
| Haiku 4.5 | $0.00002 | $0.00240 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- updated-new-function — 88% identical, 287 lines differ
How it starts
The opening of the file, as written. The whole thing — 224 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/agent-essentials
This document outlines the steps taken to implement a new function in @commercetools/agent-essentials 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.
- 2d ago First seen · 224 lines · 16 tokens per session scan A 03613db4863b
updated-new-function is a cursor rule published in the GitHub repository commercetools/mcp-essentials (13 stars, last pushed 15d ago), licensed MIT. It adds 16 tokens to every session and 2,404 once invoked, about $0.0001 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-30.
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…