cursorrules

A set of rules for building with FavCRM, a customer-management system. It tells the coding agent how to discover FavCRM tools and handle risky actions.

In plain words
What is it for?
It is for building FavCRM features, finding available tools, using domain procedures for billing, bookings, and sign-in, and safely previewing changes.
Why use it?
It reduces guesswork about API endpoints and adds a confirmation step before actions such as refunds, cancellations, or bulk messages.

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

Made for: Cursor.

Per session 90 This file is loaded in full into every session.
When invoked 90 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.00090 $0.00090
Opus 5 $0.00045 $0.00045
Sonnet 5 $0.00018 $0.00018
Haiku 4.5 $0.00009 $0.00009

Measured yesterday against content hash 069b1f9ef652, 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 yesterday.

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 · 5 lines

What it actually says

When building with FavCRM:

  1. Do not guess API endpoints. Use the FavCRM MCP server and run list_tools to discover the 150+ available tools.
  2. For specific domain logic (billing, bookings, auth), run npx skills add favcrm/mcp to download our official AI operating procedures.
  3. Always preview data and request user confirmation before destructive actions (refunds, cancellations, bulk emails/SMS).
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. yesterday First seen · 5 lines · 90 tokens per session scan A 069b1f9ef652

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository favcrm/mcp (0 stars, last pushed 6d ago), licensed MIT. It adds 90 tokens to every session, about $0.0005 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.