python-style

A set of rules for writing Python code with consistent type annotations, functional programming practices, code organization, and tests.

In plain words
What is it for?
Use it when creating or reviewing Python functions, classes, data transformations, and tests, especially when you want typed and mostly side-effect-free code.
Why use it?
It reduces ambiguity about how Python code should be written and makes data flow, side effects, and expected values easier to understand.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/yeison-liscano/http_mcp/python-style
Clone the repo
git clone --depth 1 https://github.com/yeison-liscano/http_mcp

Made for: Cursor.

Per session 367 This file is loaded in full into every session.
When invoked 367 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00367 $0.00367
Opus 5 $0.00183 $0.00183
Sonnet 5 $0.00073 $0.00073
Haiku 4.5 $0.00037 $0.00037

Measured today against content hash ed3ce3306644, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

python-style 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 today.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.cursor/rules/python-style.mdc · 50 lines

What it actually says

Python Style Guide and Best Practices

Type Hints

  • All function parameters MUST have type hints
  • All function return values MUST have type hints
  • All class attributes MUST have type hints
  • Use collections.abc for abstract base classes (Sequence, Mapping, Set, etc.)
  • Use built-in types for simple type hints (str, int, bool, list, dict, etc.)
  • Use type | None instead of Optional[type]
  • Example:
    from collections.abc import Sequence
    
    def process_data(items: Sequence[str], max_items: int | None = None) -> dict[str, int]:
        ...
    

Functional Programming Paradigm

  • Prefer pure functions over methods with side effects
  • Use immutable data structures when possible, prefer tuples over lists
  • Avoid modifying function arguments
  • Use list/dict comprehensions instead of loops when possible
  • Minimize global state and mutable variables
  • Return new values instead of modifying existing ones
  • Example:
    # Good - Pure function, immutable
    def transform_data(data: list[int]) -> list[int]:
        return [x * 2 for x in data if x > 0]
    
    # Bad - Modifies input, has side effects
    def transform_data(data: list[int]) -> None:
        for i in range(len(data)):
            data[i] *= 2
    

Code Organization

  • Keep functions small and focused on a single responsibility
  • Use composition over inheritance
  • Prefer dependency injection over global state
  • Use descriptive variable names that reflect their purpose

Testing

  • Write unit tests for all pure functions
  • Test edge cases and error conditions
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. today First seen · 50 lines · 367 tokens per session scan A ed3ce3306644

Subscribe to this mod's changes

python-style is a cursor rule published in the GitHub repository yeison-liscano/http_mcp (0 stars, last pushed 5d ago), licensed MIT. It adds 367 tokens to every session, about $0.0018 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-08-31.

Related

Other cursor rules, from other repositories

writing-guidelines

This guide ensures consistent, high-quality documentation across all Igniter.js content types (blog, docs, templates, updates). It's designed for both human authors and AI agents to produce excellent developer experiences.

felipebarcelospro/igniter-js · 7,873 tokens

browser

Provides a comprehensive and mandatory training guide for effectively utilizing browser automation tools, specifically Playwright, for research, debugging, and autonomous validation.

felipebarcelospro/igniter-js · 7,925 tokens

igniter-patterns

This guide provides a COMPLETE, ACCURATE, and MANDATORY reference for creating controllers and actions in Igniter.js. It incorporates established architectural patterns, coding best practices, and lessons learned from real-world implementations, ensuring strict adherence for all future development.

felipebarcelospro/igniter-js · 8,510 tokens

planning

Complete feature development lifecycle using memory-backed planning. Creates requirements, design, and task memories. Use when: starting new features, planning implementations, organizing development work, managing project specifications.

felipebarcelospro/igniter-js · 5,475 tokens

frontend

This rule provides comprehensive guidance for front-end development in Igniter.js + Next.js + Shadcn UI projects, ensuring consistent architecture, component patterns, and seamless integration with existing workflows.

felipebarcelospro/igniter-js · 6,832 tokens

igniter-client-usage

Comprehensive guide to using the Igniter.js Client, covering server-side and client-side usage patterns, React hooks (useQuery, useMutation, useRealtime), context management, realtime features, and best practices. This rule explains the universal client architecture and how it works seamlessly across different Next.js…

felipebarcelospro/igniter-js · 5,663 tokens