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/brunogama/ios-cursor-rules/location-rulegit clone --depth 1 https://github.com/brunogama/ios-cursor-rulesWrote 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/brunogama/ios-cursor-rules/location-rule)<a href="https://agentmods.dev/rules/brunogama/ios-cursor-rules/location-rule"><img src="https://agentmods.dev/badge/rules/brunogama/ios-cursor-rules/location-rule.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.00000 | $0.00493 |
| Opus 5 | $0.00000 | $0.00246 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
location-rule 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 3d 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.
This is a copy
89% identical to cursor-rules-location — 6 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
description: Cursor Rules Location globs: *.mdc
Cursor Rules Location
Rules for placing and organizing Cursor rule files in the repository.
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.
- 3d ago First seen · 80 lines · 493 tokens per session scan A f53fc30870cd
location-rule is a cursor rule published in the GitHub repository brunogama/ios-cursor-rules (74 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 493 tokens. A static security scan graded it A with 0 findings. It is 89% identical to cursor-rules-location, differing in 6 lines, and is treated as a copy.
Other cursor rules, from other repositories
swiftui
Rules for IcySky, a SwiftUI project for a bluesky client.
202-swift-standards-detailed
Swift 6.2 + iOS 18-26 编码规范 - 详细参考.
ipa-upload-automation
Universal IPA upload automation (TestFlight + optional App Store submission) for Flutter, React Native, and native Swift/Xcode projects.
121-swift-core
121: Core Swift development principles and modern iOS best practices.
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.