cursorrules

A set of Cursor project rules for a Discord connection and this application's development commands. Discord is a chat platform; the rules also mention a search database and agent workflows.

In plain words
What is it for?
Use it when working on this project with Discord access, or when running its server, lint, test, and installer-build commands.
Why use it?
It tells the coding agent which Discord checks to perform and which commands to use before and after development work.

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

Made for: Cursor.

Per session 161 This file is loaded in full into every session.
When invoked 161 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.00161 $0.00161
Opus 5 $0.00081 $0.00081
Sonnet 5 $0.00032 $0.00032
Haiku 4.5 $0.00016 $0.00016

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

What it actually says

discord-mcp Cursor Rules

Session Context (Discord MCP)

You have access to a Discord bot bridge with 36 operations via a portmanteau tool, LanceDB RAG, and agentic workflows.

Before starting work:

  1. List available guilds: discord(operation="list_guilds")
  2. Check recent messages in a channel: discord(operation="get_messages", channel_id="...", limit=10)

At end of work:

  • Clean up test messages if any were sent
  • Document any rate limit changes

Key Commands

  • just serve — start full stack
  • just lint — run ruff + biome
  • just test — run tests
  • just build-native — build Tauri NSIS installer
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 · 20 lines · 161 tokens per session scan A cdedea867d71

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository sandraschi/discord-mcp (2 stars, last pushed 15d ago), licensed MIT. It adds 161 tokens to every session, about $0.0008 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.