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/ankitpro/cursor-rules-generatorWrote 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/ankitpro/cursor-rules-generator/main)<a href="https://agentmods.dev/rules/ankitpro/cursor-rules-generator/main"><img src="https://agentmods.dev/badge/rules/ankitpro/cursor-rules-generator/main/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/ankitpro/cursor-rules-generator/main"><img src="https://agentmods.dev/badge/rules/ankitpro/cursor-rules-generator/main.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.00572 | $0.00572 |
| Opus 5.5 | $0.00229 | $0.00229 |
| Sonnet 5.5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
main 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Rules Generator - Development Guidelines
📁 Modular Structure: This project uses the official Cursor
.cursor/rules/format.
🎯 Quick Context
Project Type: MCP (Model Context Protocol) Server Primary Language: TypeScript Framework: Node.js with MCP SDK Purpose: Automatically generate cursor rules by analyzing codebases
📦 Tech Stack
- Runtime: Node.js 18+
- Language: TypeScript 5.x
- MCP SDK: @modelcontextprotocol/sdk
- File Operations: Node.js fs/promises
- Git Integration: simple-git
- Pattern Matching: glob
🏗️ Project Structure
src/
├── index.ts # MCP server entry point
├── types.ts # TypeScript interfaces
├── analyzers/ # Codebase analysis modules
│ ├── dependencies.ts # Package/dependency analysis
│ ├── structure.ts # Project structure analysis
│ ├── codePatterns.ts # Code pattern detection
│ ├── gitWorkflow.ts # Git workflow analysis
│ ├── environment.ts # Environment config analysis
│ └── testing.ts # Testing setup analysis
├── generator/ # Rules generation
│ ├── cursorRulesGenerator.ts
│ └── templates/ # Template generators
└── templates/ # Pre-built templates library
├── library/ # Template definitions
└── loader.ts # Template loading utilities
📝 Code Style
- Use camelCase for functions and variables
- Use PascalCase for types and interfaces
- Use async/await for asynchronous operations
- Export functions using named exports
- Use ES modules (
.jsextensions in imports)
🔧 Key Patterns
- Analysis functions return typed interfaces from
types.ts - Template generators return formatted strings with MDC frontmatter
- MCP tools follow the SDK patterns for request/response handling
- File operations use
fs/promisesfor async file I/O
🚀 Development Commands
npm run build # Compile TypeScript
npm run dev # Watch mode
npm start # Run compiled server
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 · 77 lines · 572 tokens per session scan A 3ebdf168a884
main is a cursor rule published in the GitHub repository ankitpro/cursor-rules-generator (6 stars, last pushed 7mo ago), licensed MIT. It adds 572 tokens to every session, about $0.0023 per session on Opus 5.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-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.