deepwiki-mcp: Cursor rule for Cursor

.cursor/test.mdc

test is a cursor rule for Cursor from regenrek/deepwiki-mcp. It costs 0 tokens per session (163 once invoked), scanned A, original, MIT.

A set of project rules for JavaScript and TypeScript tests that use Vitest, a testing framework. It also specifies Node.js 22 or newer and practices for testing network requests and formatted text.

In plain words
What is it for?
Use it when writing or reviewing Vitest tests, especially tests involving fetch requests, Markdown or HTML output, global browser-like objects, and asynchronous code.
Why use it?
It keeps tests consistent and prevents shared test data or environment differences from causing misleading results.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

This is regenrek/deepwiki-mcp's own configuration. It tells Cursor how to work on deepwiki-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything deepwiki-mcp configures →

About the project

deepwiki-mcp is an MCP server that crawls documentation pages from DeepWiki and returns them as Markdown or structured page data to compatible coding tools. It is intended for developers who want to bring repository documentation into editors such as Cursor. The catalogue rules use this server's documentation-fetching workflow.

regenrek/deepwiki-mcp · 1,386 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to regenrek/deepwiki-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/regenrek/deepwiki-mcp/main/.cursor/test.mdc
Clone the repo
git clone --depth 1 https://github.com/regenrek/deepwiki-mcp

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for test

README.md
[![agentmods](https://agentmods.dev/badge/rules/regenrek/deepwiki-mcp/test/github.svg)](https://agentmods.dev/rules/regenrek/deepwiki-mcp/test)
Your own site
<a href="https://agentmods.dev/rules/regenrek/deepwiki-mcp/test"><img src="https://agentmods.dev/badge/rules/regenrek/deepwiki-mcp/test/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for test

Your own site · 80×15
<a href="https://agentmods.dev/rules/regenrek/deepwiki-mcp/test"><img src="https://agentmods.dev/badge/rules/regenrek/deepwiki-mcp/test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 163 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00163
Opus 5.5 $0.00000 $0.00065
Sonnet 5.5 $0.00000 $0.00033
Haiku 4.5 $0.00000 $0.00016

Measured 2mo ago against content hash a4375e8f89ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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

Copies of this mod

1 near-identical copy found in the catalogue:

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

What it actually says

  • Always use vitest (never use jest or any other testing framework)
  • Always pin Vitest ≥ 3.1 (or latest) in devDependencies so vi.stubGlobal, unstubGlobals, and other modern helpers exist.
  • Use environment: 'node' and Node 22+ so the built-in fetch and Headers classes are available without polyfills.
  • Trim or normalise strings before comparing multi-line Markdown/HTML: expect(result.trim()) rather than raw literals with trailing spaces.
  • Always place async fetch stubs inside each test (or beforeEach) so they do not bleed unexpected data into other cases.
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. 2mo ago First seen · 10 lines · 0 tokens per session scan A a4375e8f89ef

Subscribe to this mod's changes

test is a cursor rule published in the GitHub repository regenrek/deepwiki-mcp (1,386 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 163 tokens. 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.