code-patterns

code-patterns is a cursor rule for Cursor from divar-ir/ai-doc-gen. It costs 0 tokens per session (636 once invoked), scanned A, original, MIT.

A set of Python coding rules and recurring patterns for configuration, logging, errors, file paths, and asynchronous operations. It also defines naming, formatting, type-hinting, and configuration conventions.

In plain words
What is it for?
Use it when adding Python handlers, configuration fields, environment-variable handling, file-path logic, or code that runs asynchronously.
Why use it?
It gives contributors one shared standard for writing and checking code in the project, reducing inconsistent styles and common implementation mistakes.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when adding Python handlers, configuration fields, environment-variable handling, file-path logic, or code that runs asynchronously.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/divar-ir/ai-doc-gen/code-patterns
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/divar-ir/ai-doc-gen

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 code-patterns

README.md
[![agentmods](https://agentmods.dev/badge/rules/divar-ir/ai-doc-gen/code-patterns/github.svg)](https://agentmods.dev/rules/divar-ir/ai-doc-gen/code-patterns)
Your own site
<a href="https://agentmods.dev/rules/divar-ir/ai-doc-gen/code-patterns"><img src="https://agentmods.dev/badge/rules/divar-ir/ai-doc-gen/code-patterns/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.

agentmods 80×15 button for code-patterns

Your own site · 80×15
<a href="https://agentmods.dev/rules/divar-ir/ai-doc-gen/code-patterns"><img src="https://agentmods.dev/badge/rules/divar-ir/ai-doc-gen/code-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 636 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00636
Opus 5.5 $0.00000 $0.00254
Sonnet 5.5 $0.00000 $0.00127
Haiku 4.5 $0.00000 $0.00064

Measured 1mo ago against content hash dbf6d957d057, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

code-patterns 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.

.cursor/rules/code-patterns.mdc · 55 lines

How it starts

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

Code Patterns

Style

  • Ruff: 120-char lines, 4-space indent, target-version = "py313"; import sorting enabled — run uv run ruff format src/ && uv run ruff check src/.
  • Type hints everywhere; pathlib.Path for all file paths (never strings); Pydantic BaseModel for all config/data structures.
  • Naming: snake_case files/functions, PascalCase classes, _private methods, UPPER_SNAKE constants, config classes end in Config.

Configuration

class MyHandlerConfig(BaseHandlerConfig, MyAgentConfig):
    exclude_feature: bool = Field(default=False, description="Exclude feature")  # description feeds CLI --help
  • Every Field needs a description — CLI arguments are generated from it (--exclude-feature, store_true, default None = "not specified").
  • Load order: Pydantic defaults < .ai/config.yaml (dot-notation section keys) < CLI args, merged with merge_dicts().
  • Env vars in src/config.py: required → os.environ["KEY"]; optional → os.getenv("KEY", "default") with int()/float()/str_to_bool() conversion.

Async and concurrency

  • All handler/agent operations are async; handlers implement async def handle(self).
  • Bounded concurrency: use WorkerPool from src/utils/worker_pool.py (WorkerPool(max_workers=0) = CPU count) for many tasks; asyncio.gather(*tasks, return_exceptions=True) for a fixed small set.
  • Always isolate errors: check each result with isinstance(result, Exception), log with exc_info=True, continue.

Error handling

  • Partial success is acceptable: warn and continue if some agents fail; raise ValueError only on complete failure.
  • Guarantee cleanup with try/finally (e.g., cronjob project cleanup).
  • Inside agent tools, raise ModelRetry (from pydantic_ai) for recoverable errors — file not found, permission denied.

Logging and tracing

from utils import Logger

Logger.init(logs_dir)                      # once per execution, before any use
Logger.info("Agent completed", {"total_tokens": usage.total_tokens})  # structured dict payload
Logger.error("Failed", exc_info=True)      # always exc_info=True for errors

Read the full file on GitHub · 55 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. 1mo ago First seen · 55 lines · 0 tokens per session scan A dbf6d957d057

Subscribe to this mod's changes

code-patterns is a cursor rule published in the GitHub repository divar-ir/ai-doc-gen (767 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 636 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-30.

Related

Other cursor rules, from other repositories

python-style

A set of required conventions for writing Python 3.12 code, including type notation, data structures, imports, line length, and Ruff checks. Ruff is a tool that finds style and common code problems.

Lawofall/AgentCore · 0 tokens

database-algorithm-rules

Database algorithm rules guide Python applications that store and retrieve data, including containerized services. They cover schema design, indexes, query efficiency, transactions, connection pools, caching, retries, and migrations.

holtwood/awesome-cursorrules-zh · 3 tokens

python-django-general

General coding guidance for Python and Django projects, including naming, formatting, modular apps, built-in tools, and maintainable structure. Python is a programming language, and Django is a Python web framework.

holtwood/awesome-cursorrules-zh · 195 tokens

python-general-coding-standards

A set of general standards for Python projects, including type hints, input checking, code style, security, web requests, background work, and tests. It also covers FastAPI-specific tasks such as CORS and authentication.

holtwood/awesome-cursorrules-zh · 140 tokens

python-general-style

Python style rules covering functional code, reusable modules, descriptive names, file naming, and a pattern where a function receives one object and returns one object.

holtwood/awesome-cursorrules-zh · 0 tokens

django-models

A small set of rules for Django models, the Python framework's definitions of database-backed data. It also guides how Django code should access and validate that data.

holtwood/awesome-cursorrules-zh · 78 tokens