test-scripts

A testing rule for this project: test scripts must not be run with node -e. Instead, a TypeScript test file must be written, built, and executed.

In plain words
What is it for?
Running the project's test scripts using the required TypeScript-file and build process.
Why use it?
It prevents a command-line testing approach that the project says will fail.

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/tuanldv/mcp-openapi-server-demo/test-scripts
Clone the repo
git clone --depth 1 https://github.com/TuanLdv/mcp-openapi-server-demo

Made for: Cursor.

Per session 49 This file is loaded in full into every session.
When invoked 49 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00049 $0.00049
Opus 5 $0.00024 $0.00024
Sonnet 5 $0.00010 $0.00010
Haiku 4.5 $0.00005 $0.00005

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

Security

Grade A, and why

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

This is a copy

100% identical to test-scripts — 0 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.

.cursor/rules/test-scripts.mdc · 6 lines

What it actually says

Never try to run a test-script from commandline using node -e. This will always fail, you'll need to write a typescript test file, build that and execute that.

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 · 6 lines · 49 tokens per session scan A bf5a72f6425e

Subscribe to this mod's changes

test-scripts is a cursor rule published in the GitHub repository TuanLdv/mcp-openapi-server-demo (0 stars, last pushed 10d ago), licensed MIT. It adds 49 tokens to every session, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to test-scripts, differing in 0 lines, and is treated as a copy.