cursorrules

A set of coding rules and test instructions, including rules for random values such as UUIDs, passwords, dice rolls, and numbers. It also specifies project conventions for Jest, TypeScript files, and the built-in fetch function.

In plain words
What is it for?
Use it when adding code or tests in this project, especially when random values, Jest, type declarations, mocks, or network requests are involved.
Why use it?
It keeps implementation and testing aligned with the project’s existing setup and asks before creating uncertain files or test doubles.

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/turlockmike/mcp-rand/cursorrules
Clone the repo
git clone --depth 1 https://github.com/turlockmike/mcp-rand

Made for: Cursor.

Per session 75 This file is loaded in full into every session.
When invoked 75 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.00075 $0.00075
Opus 5 $0.00037 $0.00037
Sonnet 5 $0.00015 $0.00015
Haiku 4.5 $0.00007 $0.00007

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

Security

Grade A, and why

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

Origin

This is a copy

100% identical to cursorrules — 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.

.cursorrules · 5 lines

What it actually says

  • jest config is located in jest.config.mjs and jest.setup.ts
  • Implement tests first, run tests after implementation to verify.
  • Don't create new d.ts files. Ask the user first what to do.
  • Don't create random mocks. Ask the user first.
  • Node 18 and after use fetch (based on undici), don't install anything else.
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 · 5 lines · 75 tokens per session scan A 92a9443370ac

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository turlockmike/mcp-rand (3 stars, last pushed 1y ago), licensed MIT. It adds 75 tokens to every session, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cursorrules, differing in 0 lines, and is treated as a copy.