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.
git clone --depth 1 https://github.com/AcKeskin/contextureWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/ackeskin/contexture/python)<a href="https://agentmods.dev/rules/ackeskin/contexture/python"><img src="https://agentmods.dev/badge/rules/ackeskin/contexture/python/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/ackeskin/contexture/python"><img src="https://agentmods.dev/badge/rules/ackeskin/contexture/python.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01117 |
| Opus 5.5 | $0.00000 | $0.00447 |
| Sonnet 5.5 | $0.00000 | $0.00223 |
| Haiku 4.5 | $0.00000 | $0.00112 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generated from
architectural-rules/python/— do not hand-edit.
Python errors and resources
Catch the most specific exception type. Never a bare except: — it swallows SystemExit and KeyboardInterrupt. Use except Exception: only at a top-level boundary, and re-raise or log.
Keep the try body minimal — only the line that can raise. A fat try block catches failures you didn't mean to catch.
Manage resources (files, locks, connections) with with. Deterministic release at block exit — do not rely on __del__ or GC timing.
Preserve context when re-raising: raise NewError(...) from err. Bare raise NewError(...) inside an except loses the original cause.
Why: a bare except turns Ctrl-C and clean shutdown into a hang, and GC-timed resource release leaks file handles under load. Source: Google Python Style Guide.
Python idioms
Prefer EAFP ("easier to ask forgiveness than permission") — try/except around the operation — over LBYL pre-checks where it reads cleaner and avoids time-of-check/time-of-use races.
Use comprehensions for simple transforms: one for clause, at most one filter. If it needs more, use an explicit loop — readability beats density.
Use implicit falsiness for emptiness (if not items:), but if x is None: for None — do not conflate None with empty or zero.
Never use a mutable object ([], {}, set()) as a default argument — it is created once and shared across all calls. Default to None and construct inside the body.
Why: the mutable-default-argument trap is a silent shared-state bug that survives review; conflating None with falsy is the other classic Python footgun. Source: Google Python Style Guide.
Python naming and layout
Casing per PEP 8: snake_case for functions, variables, methods, modules; CapWords for classes and exceptions (suffix error types with Error); ALL_CAPS_WITH_UNDERSCORES for module-level constants. Packages are short, all-lowercase, no underscores.
Mark non-public names with a single leading underscore (_internal). Reserve the double leading underscore (__x) for name-mangling to avoid subclass clashes — not as "more private".
Never name anything l, O, or I — indistinguishable from 1 and 0 in many fonts.
4 spaces per indent level, never tabs (Python 3 forbids mixing). Two blank lines around top-level defs, one around methods.
One import per line. Group standard-library, third-party, then local, separated by blank lines. Absolute imports over relative; never wildcard from x import *.
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.
- today First seen · 55 lines · 1,117 tokens per session scan A b7d01741ccf8
python is a cursor rule published in the GitHub repository AcKeskin/contexture (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,117 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-10-27.
Other cursor rules, from other repositories
python
You are an AI assistant specialized in Python development. Your approach emphasizes.
mollify
Use Mollify (the mollify CLI / mollify MCP server) as the source of truth for Python dead code and dependency hygiene instead of grep or manual scanning. Agent-Requested.
hatch3r-python-patterns
Python 3.12+ conventions covering uv project management, Ruff lint+format, mypy strict typing, pytest parametrize, and the FastAPI/Django request-path + ORM N+1 floor.
python-code-style-for-apps
Python 3.14 code style for ArchiPy apps — formatting, imports, docstrings, errors, complexity.
python
Rules applied when working in Python files.
secure-dev-python
These rules apply to all Python code in the repository and aim to prevent common security risks through disciplined use of input validation, output encoding, and safe APIs.