meta

Rules for using Cursor to edit Markdown-based configuration files in a repository.

In plain words
What is it for?
Use them when changing .mdc files or deciding whether to edit an existing rule, create a new one, or document a file-creation decision.
Why use it?
They help preserve line endings, whitespace, formatting, file organization, and consistency between rules and the code they describe.

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/aaronontheweb/dotnet-cursor-rules/meta
Clone the repo
git clone --depth 1 https://github.com/Aaronontheweb/dotnet-cursor-rules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 420 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.00420
Opus 5 $0.00000 $0.00210
Sonnet 5 $0.00000 $0.00084
Haiku 4.5 $0.00000 $0.00042

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

Security

Grade A, and why

meta 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/meta.mdc · 59 lines

What it actually says

Cursor Rules

This document outlines the meta-rules for cursor operations in this repository.

Line Ending & Formatting Rules

  1. Line Endings

    • Don't modify existing line endings
    • Preserve CRLF/LF as found in the original file
  2. Whitespace

    • Preserve trailing whitespace where it exists
    • Maintain existing indentation style (spaces vs tabs)
    • Keep line length consistent with existing code

File Handling

  1. MDC Files

    • Always commit changes to *.mdc files directly
    • Ensure changes to *.mdc files are synchronized with their implementation
    • Maintain consistent formatting within MDC files
    • Prefer modifying existing files over creating new ones unless explicitly requested
    • When adding new content, first check if it fits within an existing rule file
  2. File Creation

    • Only create new rule files when:
      • Explicitly requested by the user
      • The content doesn't logically fit in any existing rule file
      • Creating a new file would significantly improve organization and clarity
    • Document the rationale for creating new files in their README.md

Code Style & Structure

  1. Formatting

    • Preserve existing code formatting patterns
    • Maintain consistent naming conventions
    • Keep indentation consistent with file style
  2. Organization

    • Keep file structure consistent
    • Don't move files without updating all references
    • Maintain existing import/include order

Rule Content

  1. Examples
    • Always include "do" and "don't" examples when showing specific changes to files or syntax
    • Include helpful comments that explain why an example is a "do" or a "don't"

Documentation

  1. README.md
    • Each *.mdc file is lumped into a folder with a README.md file explaining what the rule does and when it's used.
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 · 59 lines · 420 tokens per session scan A 140b95ad8d4a

Subscribe to this mod's changes

meta is a cursor rule published in the GitHub repository Aaronontheweb/dotnet-cursor-rules (134 stars, last pushed 1y ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 420 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.