python-tooling

A set of project rules for Python development that uses uv as the required tool for installing dependencies and running checks.

In plain words
What is it for?
Use it to run the project's development checks, including linting, formatting, type checking, tests, architecture checks, and environment diagnosis.
Why use it?
It gives the project one consistent way to install packages, format code, check types, run tests, and verify the setup. uv is a Python project and package manager.

Cursor rule

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/therealsavi/iopenpod/python-tooling
Clone the repo
git clone --depth 1 https://github.com/TheRealSavi/iOpenPod
Per session 232 This file is loaded in full into every session.
When invoked 232 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.00232 $0.00232
Opus 5 $0.00116 $0.00116
Sonnet 5 $0.00046 $0.00046
Haiku 4.5 $0.00023 $0.00023

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

Security

Grade A, and why

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

docs/agents/rules/python-tooling.mdc · 32 lines

What it actually says

Python tooling

Use uv for all Python work. Never invoke bare python, pip, poetry, or conda.

Dev checks

uv sync
uv run python scripts/dev.py check    # full gate
uv run python scripts/dev.py lint     # ruff check
uv run python scripts/dev.py fmt      # ruff format
uv run python scripts/dev.py types    # mypy
uv run python scripts/dev.py test     # pytest
uv run python scripts/dev.py arch     # architecture rules
uv run python scripts/dev.py doctor   # verify install / hooks
uv run iopenpod                       # run the app

Linting

  • ruff only — do not run flake8, black, isort, or pylint
  • Config: pyproject.toml ([tool.ruff], [tool.mypy])

Before marking work done

Run uv run python scripts/dev.py lint and targeted tests at minimum.

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 · 32 lines · 232 tokens per session scan A 577fcd2db6d1

Subscribe to this mod's changes

python-tooling is a cursor rule published in the GitHub repository TheRealSavi/iOpenPod (336 stars, last pushed 2d ago), licensed MIT. It adds 232 tokens to every session, about $0.0012 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-30.