cursorrules

Project rules for developing the WeChat Developer Tools connection described here, covering its file structure, coding style, tool registration, and supported project modes.

In plain words
What is it for?
Use them when modifying this MCP server, adding tools, checking JavaScript syntax, or updating its documentation.
Why use it?
They keep changes consistent and help prevent breaking either mini-program or mini-game support.

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

Made for: Cursor.

Per session 280 This file is loaded in full into every session.
When invoked 280 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.00280 $0.00280
Opus 5 $0.00140 $0.00140
Sonnet 5 $0.00056 $0.00056
Haiku 4.5 $0.00028 $0.00028

Measured 2d ago against content hash 7bf705a112ee, 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 · 21 lines

What it actually says

Cursor / Windsurf Rules — wechat-dev-mcp

You are working inside the wechat-dev-mcp project, an MCP server that drives WeChat DevTools for both mini-programs and mini-games.

Project conventions

  • ESM ("type": "module"). Use import/export, file extensions required.
  • Entry: index.jssrc/server.jssrc/tools/*.
  • Never write to stdout except via the MCP SDK. All logs go to stderr.
  • Tool definitions live in src/tools/{common,program,game}.js; registry in src/tools/registry.js. Keep handlers small and return { content: [...] } or { isError: true, content: [...] }.
  • Mini-program-only tools must be guarded with ensureProgram() and tagged modes: ["program"] so ListTools auto-hides them for mini-games.
  • Mini-game-only tools are tagged modes: ["game"].

Before changing behavior

  1. Run node --check on edited files (no real WeChat DevTools in CI).
  2. Keep both project types working — do not break mini-program features.
  3. Document new tools in README.md and docs/MINIGAME_GUIDE.md.
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 · 21 lines · 280 tokens per session scan A 7bf705a112ee

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository jiawei686/wechat-dev-mcp (17 stars, last pushed 1mo ago), licensed MIT. It adds 280 tokens to every session, about $0.0014 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.