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/dstotijn/go-mcp/cursor-rules-locationgit clone --depth 1 https://github.com/dstotijn/go-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/dstotijn/go-mcp/cursor-rules-location)<a href="https://agentmods.dev/rules/dstotijn/go-mcp/cursor-rules-location"><img src="https://agentmods.dev/badge/rules/dstotijn/go-mcp/cursor-rules-location.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.00320 |
| Opus 5 | $0.00000 | $0.00160 |
| Sonnet 5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
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 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- cursor-rules-location — 100% identical, 4 lines differ
- cursor-rules-location — 100% identical, 4 lines differ
What it actually says
Description
This rule ensures that all new MDC (Model-Driven Code) rules are created in the .cursor/rules directory, maintaining a consistent and organized structure for rule management.
Rule
When creating new MDC rules:
- All new MDC rules MUST be created in the
.cursor/rulesdirectory - Each rule MUST be in a separate file
- Rule files MUST use the
.mdcextension - Rule files MUST follow the naming convention:
[rule-name].mdc - Rule files MUST contain proper markdown formatting
Implementation
- The Cursor IDE will enforce this rule by:
- Automatically creating new MDC rules in the
.cursor/rulesdirectory - Preventing creation of MDC rules outside this directory
- Maintaining separation of rules into individual files
- Ensuring proper file extensions and naming conventions
- Automatically creating new MDC rules in the
Benefits
- Improved organization and maintainability
- Easier rule discovery and management
- Consistent rule structure across the project
- Better version control and tracking of rule changes
Examples
✅ Correct:
.cursor/rules/
├── cursor-rules-location.mdc
├── another-rule.mdc
└── third-rule.mdc
❌ Incorrect:
.cursor/
├── rules/
│ └── cursor-rules-location.mdc
└── other-rules/
└── another-rule.mdc
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 · 45 lines · 320 tokens per session scan A d4bbd8e75542
cursor-rules-location is a cursor rule published in the GitHub repository dstotijn/go-mcp (18 stars, last pushed 1y ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 320 tokens. 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-30.
Other cursor rules, from other repositories
tdd
Final Verification: Always use: go test -v ./backend/api/handler/... | grep FAIL.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
backend
You are an expert in Go, Gin, Gorm, Gen, Cosy (https://cosy.uozi.org/) with a deep understanding of best practices and performance optimization techniques in these technologies.
refactor-large-files
Guidance for splitting large route files into maintainable pieces.
solidjs-data-fetching
Route data fetching — onMount, signals, alive guard, batch; never createResource.
seed-data
Patterns for development seed data — stable UUIDs, realistic data, cross-references.