pytest

A set of project rules for Python code changes: run pytest after a major change and run Ruff, a Python linting tool, after code changes.

In plain words
What is it for?
Projects that use pytest and Ruff and need these checks to be run at the end of development work.
Why use it?
It makes testing and code-quality checks part of the normal change process, helping catch broken behavior and common code problems.

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/pathintegral-institute/mcpm.sh/pytest
Clone the repo
git clone --depth 1 https://github.com/pathintegral-institute/mcpm.sh

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 39 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.00039
Opus 5 $0.00000 $0.00019
Sonnet 5 $0.00000 $0.00008
Haiku 4.5 $0.00000 $0.00004

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

Security

Grade A, and why

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

What it actually says

always run pytest at the end of a major change always run ruff lint at then end of any code changes

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 · 7 lines · 39 tokens per session scan A a31f0ba4cc76

Subscribe to this mod's changes

pytest is a cursor rule published in the GitHub repository pathintegral-institute/mcpm.sh (995 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 39 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.