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/cmnemoi/cursor-rulesWrote 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/cmnemoi/cursor-rules/meta-generator)<a href="https://agentmods.dev/rules/cmnemoi/cursor-rules/meta-generator"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/meta-generator/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/cmnemoi/cursor-rules/meta-generator"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/meta-generator.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.00506 |
| Opus 5.5 | $0.00000 | $0.00202 |
| Sonnet 5.5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00051 |
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 1mo 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 — 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-architecture01-standards02-programming-languages03-frameworks-and-libraries04-tools-and-configurations05-workflows-and-processes06-templates-and-models07-quality-assurance08-domain-specific-rules09-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.
*.tsxfor React) - Appropriate sub-folder: can be
features,controlleretc - 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
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.
- 1mo ago First seen · 85 lines · 0 tokens per session scan A 9e4649f7d29e
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.