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.
npx agentmods add rules/sfc-gh-cconner/support-rules-mcp/cursor-rulesgit clone --depth 1 https://github.com/sfc-gh-cconner/support-rules-mcpWrote 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.
[](https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/cursor-rules)<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/cursor-rules"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/cursor-rules.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00305 | $0.00305 |
| Opus 5 | $0.00152 | $0.00152 |
| Sonnet 5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
rule-generation 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.
What it actually says
Rule Generation Guide (Project-Wide Baseline)
Use this guide whenever you (or Cursor) create or update a rule. Rules should be small, actionable, and easy to maintain.
1) Rule File Template (copy/paste)
---
name: <domain-area> # e.g., python-type-safety
description: <one concise sentence> # what this rule enforces
alwaysApply: false # true only for core/global norms
version: 0.1.0
owners: ["@owner-or-team"]
globs: "**/*.ext, **/path/**" # comma-separated; omit if global
references:
- "@path/to/example.ext" # optional anchors
assumptions:
- <explicit assumptions; avoid guessing>
---
# <Clear Title>
## Scope
What this rule covers, what it does NOT cover.
## Guidelines (Do/Don’t)
- Do: <specific, testable guidance>
- Don’t: <anti-pattern the rule forbids>
- Defaults: <preferred library/flag/config, with reason>
## Examples
**Bad**
```<lang>
# minimal snippet that violates the rule
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.
- 2d ago First seen · 45 lines · 305 tokens per session scan A d8bb1304ad7c
rule-generation is a cursor rule published in the GitHub repository sfc-gh-cconner/support-rules-mcp (0 stars, last pushed 10mo ago), licensed Apache-2.0. It adds 305 tokens to every session, about $0.0015 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.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.