python

A set of Python coding rules covering style, imports, errors, tests, and security. Python is a programming language, and pytest is a tool for running Python tests.

In plain words
What is it for?
It is for writing and checking Python code, including running tests with uv run pytest.
Why use it?
It gives coding work consistent expectations, including type hints, documented public code, tests, and safer handling of secrets and input.

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/davidl71/project-management-automation/python
Clone the repo
git clone --depth 1 https://github.com/davidl71/project-management-automation

Made for: Cursor.

Per session 204 This file is loaded in full into every session.
When invoked 204 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.00204 $0.00204
Opus 5 $0.00102 $0.00102
Sonnet 5 $0.00041 $0.00041
Haiku 4.5 $0.00020 $0.00020

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

Security

Grade A, and why

python 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 yesterday.

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/python.mdc · 35 lines

What it actually says

Python Development Rules

Code Style

  • Follow PEP 8 conventions
  • Use type hints for function arguments and return values
  • Maximum line length: 100 characters
  • Use docstrings for all public functions and classes

Imports

  • Group imports: stdlib, third-party, local
  • Use absolute imports over relative where possible
  • Sort imports alphabetically within groups

Error Handling

  • Use specific exception types
  • Always include informative error messages
  • Log exceptions with context

Testing

  • Write tests for all new functions
  • Use pytest as the testing framework
  • Aim for >80% test coverage
  • Always use uv run pytest to run tests (never use pip install or manual venv)

Security

  • Never hardcode secrets or credentials
  • Use environment variables for configuration
  • Validate all external input
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. yesterday First seen · 35 lines · 204 tokens per session scan A 0319e11ff127

Subscribe to this mod's changes

python is a cursor rule published in the GitHub repository davidl71/project-management-automation (1 stars, last pushed 6mo ago), licensed MIT. It adds 204 tokens to every session, about $0.0010 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.