meta-generator

A set of rules for creating and organizing Cursor rule files, which give the Cursor coding assistant project-specific instructions. It defines file naming, folders, frontmatter fields, and a step-by-step approval process.

In plain words
What is it for?
Use it to generate or revise files under `.cursor/rules`, including their descriptions, file patterns, activation settings, and rule content.
Why use it?
It helps keep assistant instructions consistent and makes it easier to find or update existing rules instead of creating conflicting ones.

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

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 506 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.00506
Opus 5 $0.00000 $0.00253
Sonnet 5 $0.00000 $0.00101
Haiku 4.5 $0.00000 $0.00051

Measured yesterday against content hash 9e4649f7d29e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

meta-generator 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 yesterday.

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.

general-rules/.cursor/rules/meta-generator.mdc · 85 lines

How it starts

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

Rule Template

---
description: to_generate
globs: to_generate
alwaysApply: to_generate
---

Sub rule 1:
- Rule 1
- Rule 2

...

Steps

  • Between each steps wait for user approval.

1. Structure

  • Check if this is an existing rule to update under all .cursor/rules sub-folders
File name format
#-rule-name[@version][-specificity].mdc
Directory structure
  • Write in .cursor/rules/{folder}/{rule}.mdc

{folder}:

  • 00-architecture
  • 01-standards
  • 02-programming-languages
  • 03-frameworks-and-libraries
  • 04-tools-and-configurations
  • 05-workflows-and-processes
  • 06-templates-and-models
  • 07-quality-assurance
  • 08-domain-specific-rules
  • 09-other

2. frontmatter header

Generate description

One line. Comprehensive description that provides full context and clearly indicates when this rule should be applied. Include key scenarios, impacted areas, and why following this rule is important. While being thorough, remain focused and relevant. The description should be detailed enough that the agent can confidently determine whether to apply the rule in any given situation.

Generate globs
  • Appropriate extension language based (e.g. *.tsx for React)
  • Appropriate sub-folder: can be features, controller etc
  • Appropriate repo: apps/frontend, apps/backend

Example for React: globs: apps/frontend/**/*.tsx

Generate alwaysApply
  • Mostly false, double check if this REALLY needs to be applied globally

3. Rule content

Groups (optional)
  • Not needed for short rules content
  • Identify rule groups
  • Wait for user validation
  • No MD titles, use "Group's name :"
Generate/Change Rules content
  • Backticks for code ref
  • Bullet points only
  • Translate example into generic rule format
  • Remove non-essential, no fluff
  • Write commands only
  • 1 ultra short (3–7 words) rule per bullet point

4. Filled template

  • Write proper filled template in proper dir WITH frontmatter header

Read the full file on GitHub · 85 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. yesterday First seen · 85 lines · 0 tokens per session scan A 9e4649f7d29e

Subscribe to this mod's changes

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