python-inline-scripts_windows

A rule requiring a specific method for running short, inline Python scripts on Windows. The provided example uses uv to run a temporary script.

In plain words
What is it for?
Use it when a user explicitly asks to run Python inline on Windows.
Why use it?
It helps keep inline Python execution consistent with the required setup.

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/jahands/prompts/python-inline-scripts_windows
Clone the repo
git clone --depth 1 https://github.com/jahands/prompts
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
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 94% copy Near-identical to another mod 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.00030 $0.00183
Opus 5 $0.00015 $0.00092
Sonnet 5 $0.00006 $0.00037
Haiku 4.5 $0.00003 $0.00018

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

Security

Grade A, and why

python-inline-scripts_windows 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.

Origin

This is a copy

94% identical to python-inline-scripts — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

cursor-rules/python-inline-scripts_windows.mdc · 31 lines

What it actually says

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 · 31 lines · 30 tokens per session scan A 88e93d222bb8

Subscribe to this mod's changes

python-inline-scripts_windows is a cursor rule published in the GitHub repository jahands/prompts (19 stars, last pushed 7mo ago), licensed MIT. It adds 30 tokens to every session and 183 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to python-inline-scripts, differing in 5 lines, and is treated as a copy.