agentmods.dev

cursor-rules-meta-guide

A guide for writing and maintaining Cursor rules, which are project instructions that shape how the Cursor coding assistant works with selected files.

In plain words
What is it for?
Use it to define rule metadata, file patterns, coding requirements, good and bad examples, cross-references, and maintenance practices.
Why use it?
It helps keep rules consistent, specific, reusable, and supported by examples and references to real project files.

Cursor rule

5.7k +1 4mo ago A scan 375 tokens original MIT archived
View the source file steipete/agent-rules
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/steipete/agent-rules/cursor-rules-meta-guide
Clone the repo
git clone --depth 1 https://github.com/steipete/agent-rules
Per session 375 This file is loaded in full into every session.
When invoked 375 The same file — it is already loaded in full.
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.00375 $0.00375
Opus 5 $0.00187 $0.00187
Sonnet 5 $0.00075 $0.00075
Haiku 4.5 $0.00038 $0.00038

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

Security

Grade A, and why

cursor-rules-meta-guide 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.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

project-rules/cursor-rules-meta-guide.mdc · 53 lines

What it actually says

  • Required Rule Structure:

    ---
description: Clear, one-line description of what the rule enforces
globs: path/to/files/*.ext, other/path/**/*
alwaysApply: boolean
---

- **Main Points in Bold**
  - Sub-points with details
  - Examples and explanations

  • File References:

  • Code Examples:

    • Use language-specific code blocks
    // ✅ DO: Show good examples
const goodExample = true;

// ❌ DON'T: Show anti-patterns
const badExample = false;

  • Rule Content Guidelines:

    • Start with high-level overview
    • Include specific, actionable requirements
    • Show examples of correct implementation
    • Reference existing code when possible
    • Keep rules DRY by referencing other rules

  • Rule Maintenance:

    • Update rules when new patterns emerge
    • Add examples from actual codebase
    • Remove outdated patterns
    • Cross-reference related rules

  • Best Practices:

    • Use bullet points for clarity
    • Keep descriptions concise
    • Include both DO and DON'T examples
    • Reference actual code over theoretical examples
    • Use consistent formatting across rules
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 · 53 lines · 375 tokens per session scan A 60e89f6f5894

Subscribe to this mod's changes

cursor-rules-meta-guide is a cursor rule published in the GitHub repository steipete/agent-rules (5,695 stars, last pushed 4mo ago), licensed MIT. It adds 375 tokens to every session, about $0.0019 per session on Opus 5. 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.

Building agentsagentclaudecodecursorllmsrules
Related

Other cursor rules, from other repositories

skill-and-agent-references

Reference skills, agents, and commands by their registered name (never by filesystem path), and decompose oversized commands or agents by extracting sections into skills with by-name references.

zotoio/CRUX-Compress · 1,439 tokens

create-rule-agent

This rule is responsible for creating and updating Cursor rules. Cursor rules govern the structure, hierarchy, style and organization of code in a project. This rule should be invoked in Agent mode when: 1. a user wants to create a new cursor rule, 2. a user wants to update or change an existing rule, 3. user wants…

usrrname/cursorrules · 3,429 tokens

create-update-agent

This rule runs whenever a developer wants to create an AI agent or wants to edit an existing one in Cursor.

usrrname/cursorrules · 0 tokens

team

Tmux-based parallel agent coordination — spawn real worker processes across panes.

Jkudjo/oh-my-cursor · 13 tokens

autopilot

Fully autonomous execution — clarify, plan, and execute without interruption.

Jkudjo/oh-my-cursor · 12 tokens

cursorrules

Enhanced thinking chain and reasoning capabilities for Cursor AI Assistant | 为 Cursor AI 助手提供增强的思维链和推理能力的规则集.

kirklin/cursor-thinking · 3,164 tokens