cursorrules

A short set of project rules that points to .claude/CLAUDE.md for the full MCPSpy documentation.

In plain words
What is it for?
Use it as an entry point to the project documentation when building, testing, running integration tests, or working with Git worktrees.
Why use it?
It directs the coding agent to the project’s detailed architecture, stack, structure, build instructions, tests, and Git workflow.

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/alex-ilgayev/mcpspy/cursorrules
Clone the repo
git clone --depth 1 https://github.com/alex-ilgayev/MCPSpy

Made for: Cursor.

Per session 56 This file is loaded in full into every session.
When invoked 56 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.00056 $0.00056
Opus 5 $0.00028 $0.00028
Sonnet 5 $0.00011 $0.00011
Haiku 4.5 $0.00006 $0.00006

Measured 2d ago against content hash 9a9bc8160c9e, 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.

.cursorrules · 11 lines

What it actually says

MCPSpy Project Rules

See .claude/CLAUDE.md for complete project documentation including:

  • Project overview and architecture
  • Technology stack
  • Project structure
  • Building and running instructions
  • Testing commands
  • Integration tests
  • Git worktree workflow
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 · 11 lines · 56 tokens per session scan A 9a9bc8160c9e

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository alex-ilgayev/MCPSpy (517 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 56 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.