test

A project rule for test-driven changes: write tests for new behaviour, update them when code changes, and run the related tests. TDD means developing with tests as a central check.

In plain words
What is it for?
Use it as a development standard for adding functionality, changing code, and verifying the results with pnpm.
Why use it?
It reduces the chance that new features or refactors silently break existing behaviour.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/commercetools/mcp-essentials/test
Clone the repo
git clone --depth 1 https://github.com/commercetools/mcp-essentials

Made for: Cursor.

Per session 70 This file is loaded in full into every session.
When invoked 70 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00070 $0.00070
Opus 5 $0.00035 $0.00035
Sonnet 5 $0.00014 $0.00014
Haiku 4.5 $0.00007 $0.00007

Measured yesterday against content hash 0e574e1f12b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

test 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • test — 100% identical, 0 lines differ
.cursor/rules/test.mdc · 11 lines

What it actually says

Always follow these rules:

  • After creating a new functionality create test cases for all possible paths
  • After updating or refactoring update test cases or create new ones
  • Run related tests and make sure all pass
  • project uses pnpm as package manager
Changes

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.

  1. yesterday First seen · 11 lines · 70 tokens per session scan A 0e574e1f12b3

Subscribe to this mod's changes

test is a cursor rule published in the GitHub repository commercetools/mcp-essentials (13 stars, last pushed 15d ago), licensed MIT. It adds 70 tokens to every session, about $0.0003 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.