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/seanlf/weather-mcp/cursor-rules-locationgit clone --depth 1 https://github.com/SeanLF/weather-mcpWhat 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.00461 | $0.00461 |
| Opus 5 | $0.00230 | $0.00230 |
| Sonnet 5 | $0.00092 | $0.00092 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
cursor-rules-location 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.
This is a copy
84% identical to cursor-rules-location — 15 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
actions:
-
type: reject conditions:
- pattern: "^(?!\.\/\.cursor\/rules\/.*\.mdc$)" message: "Cursor rule files (.mdc) must be placed in the .cursor/rules directory"
-
type: suggest message: | When creating Cursor rules:
-
Always place rule files in PROJECT_ROOT/.cursor/rules/:
.cursor/rules/ ├── your-rule-name.mdc ├── another-rule.mdc └── ... -
Follow the naming convention:
- Use kebab-case for filenames
- Always use .mdc extension
- Make names descriptive of the rule's purpose
-
Directory structure:
PROJECT_ROOT/ ├── .cursor/ │ └── rules/ │ ├── your-rule-name.mdc │ └── ... └── ... -
Never place rule files:
- In the project root
- In subdirectories outside .cursor/rules
- In any other location
-
examples:
-
input: |
Bad: Rule file in wrong location
rules/my-rule.mdc my-rule.mdc .rules/my-rule.mdc
Good: Rule file in correct location
.cursor/rules/my-rule.mdc output: "Correctly placed Cursor rule file"
metadata: priority: high version: 1.0
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.
- yesterday First seen · 73 lines · 461 tokens per session scan A d4faefe5d42a
cursor-rules-location is a cursor rule published in the GitHub repository SeanLF/weather-mcp (2 stars, last pushed 1y ago), licensed MIT. It adds 461 tokens to every session, about $0.0023 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to cursor-rules-location, differing in 15 lines, and is treated as a copy.
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.