gwt-tests

A rule for writing tests in three clearly marked phases: Given for setup, When for the action being tested, and Then for checking the result. TDD means test-driven development, but this rule applies to test structure rather than requiring TDD.

In plain words
What is it for?
Use it in TypeScript test files to structure test blocks, name tests by behavior, minimize setup noise, and group assertions under the Then section.
Why use it?
It makes tests easier to read by separating preparation, execution, and verification, while keeping assertions focused on behavior.

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/virtuslab-open-source/strapi-plugin-mcp/gwt-tests
Clone the repo
git clone --depth 1 https://github.com/VirtusLab-Open-Source/strapi-plugin-mcp

Made for: Cursor.

Per session 202 This file is loaded in full into every session.
When invoked 202 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.00202 $0.00202
Opus 5 $0.00101 $0.00101
Sonnet 5 $0.00040 $0.00040
Haiku 4.5 $0.00020 $0.00020

Measured 2d ago against content hash 87f36c51cc4c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gwt-tests 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.

.cursor/rules/gwt-tests.mdc · 40 lines

What it actually says

Title: Given/When/Then test convention

Scope: tests (**/*.test.ts, **/*.spec.ts)

Rule:

  • Each test block must clearly separate three phases with comments:
    • // Given for setup
    • // When for exercising the system under test
    • // Then for assertions

Guidance:

  • Prefer one assertion group under the // Then section.
  • Keep setup minimal; use factories/helpers for noisy data.
  • Name tests in behavior terms, not implementation details.

Examples:

Bad:

it('does X', () => {
  const a = 1; doSomething(a);
  expect(result).toBe(1);
});

Good:

it('does X', () => {
  // Given
  const a = 1;

  // When
  const result = doSomething(a);

  // Then
  expect(result).toBe(1);
});
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. 2d ago First seen · 40 lines · 202 tokens per session scan A 87f36c51cc4c

Subscribe to this mod's changes

gwt-tests is a cursor rule published in the GitHub repository VirtusLab-Open-Source/strapi-plugin-mcp (3 stars, last pushed 6mo ago), licensed MIT. It adds 202 tokens to every session, about $0.0010 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-31.