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/hamzaamjad/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/hamzaamjad/cursor-rules/436-code-generation-patterns)<a href="https://agentmods.dev/rules/hamzaamjad/cursor-rules/436-code-generation-patterns"><img src="https://agentmods.dev/badge/rules/hamzaamjad/cursor-rules/436-code-generation-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.
<a href="https://agentmods.dev/rules/hamzaamjad/cursor-rules/436-code-generation-patterns"><img src="https://agentmods.dev/badge/rules/hamzaamjad/cursor-rules/436-code-generation-patterns.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.00005 | $0.00477 |
| Opus 5.5 | $0.00002 | $0.00191 |
| Sonnet 5.5 | $0.00001 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
436-code-generation-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.
What it actually says
Code Generation Patterns
Purpose: Ensure professional-grade AI-generated code without common formatting errors.
Critical Patterns
Formatting Rules
# ✅ CORRECT Structure
def process():
"""Process data."""
return data
# ❌ AVOID: Same-line docstrings
def bad(): """Wrong""" return None
Import Organization
# Standard → Third-party → Local
import os
import json
import numpy as np
import pandas as pd
from .utils import helper
from .models import DataModel
Error Handling
# Always include proper error handling
try:
result = risky_operation()
except SpecificError as e:
logger.error(f"Operation failed: {e}")
raise ProcessingError(f"Cannot process: {e}") from e
Type Safety
from typing import List, Dict, Optional
def process_items(items: List[Dict[str, Any]]) -> Optional[pd.DataFrame]:
"""Process with full type hints."""
if not items:
return None
return pd.DataFrame(items)
Common Pitfalls
- Missing newlines after docstrings/comments
- Incomplete imports - always specify full paths
- Bare exceptions - catch specific errors
- No type hints - add for public APIs
- Magic numbers - use named constants
Validation Checklist
- Proper indentation (4 spaces)
- Docstrings for public functions
- Error handling for I/O operations
- Type hints for parameters/returns
- No trailing whitespace
- Consistent quote style
Quick Fixes
# Auto-format Python
black --line-length 88 *.py
# Type checking
mypy --strict *.py
# Linting
ruff check --fix *.py
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 · 92 lines · 5 tokens per session scan A 5120ac4d65a0
436-code-generation-patterns is a cursor rule published in the GitHub repository hamzaamjad/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 5 tokens to every session and 477 once invoked, about $0.0000 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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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).