awesome-cursor-rules-mdc is a generator that creates Cursor MDC rule files from structured library information, using semantic search and language models to gather and organize guidance. Developers use it to produce reusable rules for libraries in Cursor, and the catalogue includes 200 of those rules.
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/sanjeed5/awesome-cursor-rules-mdcWrote 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/sanjeed5/awesome-cursor-rules-mdc/gensim)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/gensim"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/gensim.svg" alt="Measured on agentmods" 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.03364 | $0.03364 |
| Opus 5 | $0.01682 | $0.01682 |
| Sonnet 5 | $0.00673 | $0.00673 |
| Haiku 4.5 | $0.00336 | $0.00336 |
Grade A, and why
gensim 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 4d 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 — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gensim Best Practices
This document is your definitive guide for using gensim effectively and correctly within our team. We prioritize reproducibility, performance, and maintainability. Follow these rules to ensure consistent, high-quality NLP pipelines.
1. Ensure Reproducibility
Always configure logging and set a random seed at the entry point of any script using gensim models. This is non-negotiable for debugging and consistent results.
❌ BAD: Unpredictable Runs
import gensim
from gensim import models, corpora
# No logging, no seed
# ... model training ...
lda_model = models.LdaModel(corpus, num_topics=10)
✅ GOOD: Reproducible and Observable Runs
import logging
import numpy as np
import gensim
from gensim import models, corpora
from gensim.utils import randseed
# 1. Configure logging first
logging.basicConfig(format='%(asctime)s : %(levelname)s : %(message)s', level=logging.INFO)
# 2. Set a global random seed for gensim and numpy
# Gensim's randseed sets numpy's seed internally.
randseed = 42
np.random.seed(randseed)
# ... rest of your script ...
# Ensure any model that takes a random_state or seed parameter uses it
lda_model = models.LdaModel(corpus, num_topics=10, random_state=randseed)
2. Construct Clean and Efficient Corpora
A well-prepared corpus is fundamental to effective topic modeling. Prioritize memory efficiency and intelligent vocabulary pruning.
2.1. Preprocessing with gensim.utils.simple_preprocess and spaCy
Combine gensim's simple preprocessing with spaCy for robust tokenization and lemmatization. simple_preprocess handles basic tokenization and lowercasing efficiently.
❌ BAD: Manual, Inconsistent Preprocessing
import re
documents = ["This is a document.", "Another document here."]
stoplist = set('is a here'.split())
texts = []
for doc in documents:
# Manual lowercasing, splitting, and stopword removal
tokens = [word for word in re.findall(r'\b\w+\b', doc.lower()) if word not in stoplist]
texts.append(tokens)
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.
- 4d ago First seen · 386 lines · 3,364 tokens per session scan A c7d7fe6081db
gensim is a cursor rule published in the GitHub repository sanjeed5/awesome-cursor-rules-mdc (3,571 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 3,364 tokens to every session, about $0.0168 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-09-03.
Other cursor rules, from other repositories
tensorflow
TensorFlow: Keras, model training, production deployment.
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.
cli-error-handling
CLI command error handling patterns.
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.