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.
git clone --depth 1 https://github.com/smeubank/cursor-templateWrote 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/smeubank/cursor-template/document-scopes)<a href="https://agentmods.dev/rules/smeubank/cursor-template/document-scopes"><img src="https://agentmods.dev/badge/rules/smeubank/cursor-template/document-scopes/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/smeubank/cursor-template/document-scopes"><img src="https://agentmods.dev/badge/rules/smeubank/cursor-template/document-scopes.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01576 |
| Opus 5.5 | $0.00000 | $0.00630 |
| Sonnet 5.5 | $0.00000 | $0.00315 |
| Haiku 4.5 | $0.00000 | $0.00158 |
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 2mo 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.
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
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.
- 2mo ago First seen · 182 lines · 0 tokens per session scan A 691217f89a32
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.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
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.