gensim

gensim is a cursor rule for Cursor from sanjeed5/awesome-cursor-rules-mdc. It costs 3,364 tokens per session, scanned A, original, CC0-1.0.

A set of team rules for using gensim, a Python library for analysing text and finding topics in large collections of documents.

In plain words
What is it for?
Use it when building text-processing pipelines, preparing document collections, or training topic models.
Why use it?
It helps make model results repeatable and the code easier to debug and maintain.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it when building text-processing pipelines, preparing document collections, or training topic models.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/sanjeed5/awesome-cursor-rules-mdc/gensim
About the project

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.

sanjeed5/awesome-cursor-rules-mdc · 3,571 stars · on GitHub

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.

Clone the repo
git clone --depth 1 https://github.com/sanjeed5/awesome-cursor-rules-mdc

Made for: Cursor.

Wrote 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.

agentmods badge for gensim

README.md
[![agentmods](https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/gensim.svg)](https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/gensim)
Your own site
<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>
Per session 3,364 This file is loaded in full into every session.
When invoked 3,364 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.03364 $0.03364
Opus 5 $0.01682 $0.01682
Sonnet 5 $0.00673 $0.00673
Haiku 4.5 $0.00336 $0.00336

Measured 4d ago against content hash c7d7fe6081db, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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.

rules-mdc/gensim.mdc · 386 lines

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)

Read the full file on GitHub · 386 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. 4d ago First seen · 386 lines · 3,364 tokens per session scan A c7d7fe6081db

Subscribe to this mod's changes

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.