010-python-tooling

Project rules for developing Python code in this codebase. They specify Python 3.12 or newer, the uv package manager, Ruff for linting and formatting, and ty for type checking.

In plain words
What is it for?
Installing Python packages, running commands in the project environment, formatting and linting code, checking types, and declaring dependencies in pyproject.toml.
Why use it?
They prevent developers from using inconsistent tools or putting dependencies in the wrong place. Following them keeps Python commands and code checks consistent across the project.

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/wshobson/agents/010-python-tooling
Clone the repo
git clone --depth 1 https://github.com/wshobson/agents

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 183 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00183
Opus 5 $0.00000 $0.00092
Sonnet 5 $0.00000 $0.00037
Haiku 4.5 $0.00000 $0.00018

Measured 2d ago against content hash 3571a78350ed, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

010-python-tooling 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 2d 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/010-python-tooling.mdc · 17 lines

What it actually says

Python tooling

This project uses the Astral Rust toolchain:

  • uv for package management. Run uv run <cmd> to execute inside the venv, uv add <pkg> to install.
  • ruff for linting and formatting. uv run ruff check . / uv run ruff format ..
  • ty for type checking. uv run ty check ..

Do not use pip, mypy, or black. Do not edit requirements.txt for Python deps — those belong in pyproject.toml.

Python ≥ 3.12 is required. Use modern syntax (X | Y, list[T], structural pattern matching).

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. 2d ago First seen · 17 lines · 0 tokens per session scan A 3571a78350ed

Subscribe to this mod's changes

010-python-tooling is a cursor rule published in the GitHub repository wshobson/agents (39,318 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 183 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.