document-scopes

A map of the roles and boundaries of project rule and documentation files, including high-level navigation, architecture, and reusable coding patterns.

In plain words
What is it for?
Use it to decide what belongs in files such as cursor.mdc, README.md, architecture.mdc, and common-patterns.mdc, and to keep project guidance organized.
Why use it?
It prevents multiple files from giving overlapping or conflicting instructions and helps developers find the right document for a question.

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/smeubank/cursor-template/document-scopes
Clone the repo
git clone --depth 1 https://github.com/smeubank/cursor-template

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,576 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.01576
Opus 5 $0.00000 $0.00788
Sonnet 5 $0.00000 $0.00315
Haiku 4.5 $0.00000 $0.00158

Measured 2d ago against content hash 691217f89a32, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

document-scopes 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.

.cursor/rules/llms/document-scopes.mdc · 182 lines

How it starts

The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Document Scopes

🎯 Purpose

This document defines the purpose and scope of each .cursor/rules/*.mdc file to prevent overlap and ensure comprehensive coverage.

📚 Core Navigation Files

cursor.mdc

  • Purpose: Primary navigation and project overview
  • Scope: High-level project context, essential commands, critical constraints
  • Audience: First point of contact for AI assistants
  • Content: Links to detailed guides, not implementation details

README.md

  • Purpose: Documentation structure explanation
  • Scope: How to use the documentation system
  • Audience: Developers and AI assistants
  • Content: File organization, usage instructions, design principles

🏗️ Architecture & Structure

architecture.mdc

  • Purpose: System design and technology decisions
  • Scope: Repository structure, technology stack, architectural patterns
  • Audience: Developers making structural decisions
  • Content: Directory structure, deployment architecture, performance considerations
  • Excludes: Implementation details, code examples

common-patterns.mdc

  • Purpose: Reusable code patterns and conventions
  • Scope: Standard implementations used across the project
  • Audience: Developers implementing features
  • Content: Code patterns, not business logic or specific features
  • Excludes: Domain-specific business rules, one-off implementations

🛠️ Implementation Guides

coding-guidelines.mdc

  • Purpose: Code quality and style standards
  • Scope: TypeScript, Next.js, and database conventions
  • Audience: Developers writing code
  • Content: Language standards, framework patterns, quality checklists
  • Excludes: Business logic, architecture decisions

monitoring.mdc

  • Purpose: Observability and error tracking
  • Scope: Sentry integration, logging patterns, performance monitoring
  • Audience: Developers implementing monitoring
  • Content: Logging utilities, error handling, performance tracking
  • Excludes: Business metrics, domain-specific analytics

Read the full file on GitHub · 182 lines

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. 2d ago First seen · 182 lines · 0 tokens per session scan A 691217f89a32

Subscribe to this mod's changes

document-scopes is a cursor rule published in the GitHub repository smeubank/cursor-template (6 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,576 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-31.