cursorrules

A set of rules linking the MCP protocol, a standard way for AI tools to communicate, with Chrome extensions and browser features.

In plain words
What is it for?
Use it for agent workflows that need repeated feedback and access to browser capabilities through Chrome extensions.
Why use it?
It tells the agent how to request user feedback during every stage of a task and when to stop asking for it.

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/2019-02-18/mcx/cursorrules
Clone the repo
git clone --depth 1 https://github.com/2019-02-18/MCX

Made for: Cursor.

Per session 170 This file is loaded in full into every session.
When invoked 170 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.00170 $0.00170
Opus 5 $0.00085 $0.00085
Sonnet 5 $0.00034 $0.00034
Haiku 4.5 $0.00017 $0.00017

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

What it actually says

MCP mcp-feedback-enhanced 规则

  1. 在任何流程、任务、对话进行时,无论是询问、回复、或完成阶段性任务,皆必须调用 MCP mcp-feedback-enhanced。
  2. 每当收到用户反馈,若反馈内容非空,必须再次调用 MCP mcp-feedback-enhanced,并根据反馈内容调整行为。
  3. 仅当用户明确表示「结束」或「不再需要交互」时,才可停止调用 MCP mcp-feedback-enhanced,流程才算结束。
  4. 除非收到结束指令,否则所有步骤都必须重复调用 MCP mcp-feedback-enhanced。
  5. 完成任务前,必须使用 MCP mcp-feedback-enhanced 工具向用户询问反馈。
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 · 7 lines · 170 tokens per session scan A d8e39ccd0527

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository 2019-02-18/MCX (1 stars, last pushed 1y ago), licensed MIT. It adds 170 tokens to every session, about $0.0009 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-31.