xmcp: Cursor rule for Cursor

.cursorrules

cursorrules is a cursor rule for Cursor from vibeforge1111/xmcp. It costs 626 tokens per session, scanned A, original, MIT.

A set of rules for retrieving and analyzing articles published on X, formerly known as Twitter. It requires using a browser-based article tool because these pages need JavaScript to load their content.

In plain words
What is it for?
Use it when an agent must fetch or analyze an X article or a matching Twitter article URL.
Why use it?
Simple web requests may return empty or incomplete X articles. These rules direct the agent to the method that can render and read them correctly.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/. Also seen: mentions Cursor.

This is vibeforge1111/xmcp's own configuration. It tells Cursor how to work on xmcp 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 xmcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to vibeforge1111/xmcp. 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/vibeforge1111/xmcp/main/.cursorrules
Clone the repo
git clone --depth 1 https://github.com/vibeforge1111/xmcp

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 cursorrules

README.md
[![agentmods](https://agentmods.dev/badge/rules/vibeforge1111/xmcp/cursorrules/github.svg)](https://agentmods.dev/rules/vibeforge1111/xmcp/cursorrules)
Your own site
<a href="https://agentmods.dev/rules/vibeforge1111/xmcp/cursorrules"><img src="https://agentmods.dev/badge/rules/vibeforge1111/xmcp/cursorrules/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 cursorrules

Your own site · 80×15
<a href="https://agentmods.dev/rules/vibeforge1111/xmcp/cursorrules"><img src="https://agentmods.dev/badge/rules/vibeforge1111/xmcp/cursorrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 626 This file is loaded in full into every session.
When invoked 626 The same file — it is already loaded in full.
Security scan A 1 finding. 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.00626 $0.00626
Opus 5.5 $0.00250 $0.00250
Sonnet 5.5 $0.00125 $0.00125
Haiku 4.5 $0.00063 $0.00063

Measured 2mo ago against content hash 47db7fea99d5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cursorrules scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

2. **NEVER use WebFetch, curl, or requests** - they will return empty/broken content
.cursorrules · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cursor Rules for XMCP

CRITICAL: X/Twitter Article Fetching

When the user asks you to read, fetch, or analyze an X/Twitter article:

  1. ALWAYS use the get_article MCP tool - it uses Playwright to render JavaScript
  2. NEVER use WebFetch, curl, or requests - they will return empty/broken content
  3. X articles require JavaScript rendering - only Playwright works

Correct Pattern

User: "Read this X article: https://x.com/user/status/123"
You: Use mcp__x-twitter__get_article with the URL

Wrong Pattern (DO NOT DO THIS)

User: "Read this X article"
You: WebFetch("https://x.com/...")  # WRONG - will fail
You: requests.get("https://x.com/...")  # WRONG - will fail

Article URLs That Need Playwright

Any URL matching these patterns requires get_article:

  • https://x.com/*/status/*
  • https://twitter.com/*/status/*
  • https://x.com/i/article/*
  • https://twitter.com/i/article/*

Available MCP Tools

The x-twitter MCP provides these tool categories:

Research (Read-Only)

  • search_twitter - Search with engagement metrics
  • search_articles - Find tweets with articles
  • get_article - Fetch article content (USES PLAYWRIGHT)
  • get_user_profile, get_user_by_screen_name - User info
  • get_tweet_details - Tweet info
  • get_trends - Trending topics

Engagement

  • favorite_tweet / unfavorite_tweet - Like/unlike
  • retweet / unretweet - Retweet
  • bookmark_tweet - Save tweets

Publishing

  • post_tweet - Post a tweet
  • create_thread - Post a thread
  • quote_tweet - Quote tweet
  • create_poll_tweet - Create poll

Conversations

  • get_conversation - Get full thread
  • get_replies - Get replies to a tweet

Permissions

Tools are permission-gated by profile. If a tool fails with "not enabled":

  • Default profile is researcher (read-only)
  • Publishing requires creator profile
  • Social actions require manager profile

When User Mentions Twitter/X

  1. If they want to search: Use search_twitter
  2. If they want to read an article: Use get_article (PLAYWRIGHT)
  3. If they want to see a thread: Use get_conversation
  4. If they want to post: Use post_tweet or create_thread
  5. If they want user info: Use get_user_by_screen_name

Read the full file on GitHub · 73 lines

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 · 73 lines · 626 tokens per session scan A 47db7fea99d5

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository vibeforge1111/xmcp (19 stars, last pushed 9mo ago), licensed MIT. It adds 626 tokens to every session, about $0.0025 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other cursor rules, from other repositories