python

A set of Python coding standards for NEMESIS, a security-analysis project. It specifies type annotations, asynchronous input and output, data models, and related implementation practices.

In plain words
What is it for?
Use it when writing or reviewing Python modules, defining functions, handling subprocesses or network and database access, creating data models, or coordinating independent tasks.
Why use it?
It keeps code interfaces explicit and helps prevent slow or blocking operations from disrupting asynchronous work.

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/joaovicdev/nemesis/python
Clone the repo
git clone --depth 1 https://github.com/joaovicdev/nemesis

Made for: Cursor.

Per session 569 This file is loaded in full into every session.
When invoked 569 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.00569 $0.00569
Opus 5 $0.00284 $0.00284
Sonnet 5 $0.00114 $0.00114
Haiku 4.5 $0.00057 $0.00057

Measured yesterday against content hash 7f0d4b82282a, 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 · 67 lines

How it starts

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

Python Standards

Type Annotations

  • All function signatures MUST have type annotations — parameters and return types.
  • Use from __future__ import annotations at the top of every module to enable postponed evaluation of annotations.
  • Prefer X | Y union syntax over Optional[X] or Union[X, Y].
  • Use TypeAlias for complex types used in multiple places.
# Good
async def analyze(output: str, context: ProjectContext) -> list[Finding]: ...

# Bad
def analyze(output, context):  # no types

Async / Await

  • All I/O operations (subprocess, database, LLM calls, HTTP) MUST be async.
  • Use asyncio.create_task() for fire-and-forget background work.
  • Use asyncio.gather() for parallel independent operations (e.g. running multiple tools).
  • Never use time.sleep() — use await asyncio.sleep().
  • Never call blocking I/O in async functions — use asyncio.to_thread() if needed.

Data Models

  • Use pydantic.BaseModel for all data models exchanged between layers (Finding, Project, Session, AgentEvent, etc.).
  • Use dataclasses.dataclass only for simple internal data containers that do not cross layer boundaries.
  • All models that are persisted to SQLite must have an id: str field (UUID).

Logging

  • NEVER use print() in production code. Use logging.getLogger(__name__).
  • In TUI code, emit Textual messages/events instead of logging directly.
  • Log levels: DEBUG for raw tool output, INFO for agent state changes, WARNING for unexpected conditions, ERROR for failures.

Code Style

  • Maximum line length: 100 characters.
  • Use ruff for formatting and linting — run uv run ruff check and uv run ruff format.
  • Prefer early returns over deeply nested conditionals.
  • Prefer named constants over magic strings — define them at module level in UPPER_CASE.
  • All exceptions should be caught at boundaries (agents, tool runners) and converted to typed result objects — never let raw exceptions propagate to the TUI.

Read the full file on GitHub · 67 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. yesterday First seen · 67 lines · 569 tokens per session scan A 7f0d4b82282a

Subscribe to this mod's changes

python is a cursor rule published in the GitHub repository joaovicdev/nemesis (4 stars, last pushed 4mo ago), licensed MIT. It adds 569 tokens to every session, about $0.0028 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.