scripts

A set of coding rules for Python project scripts, including resource handling and application configuration.

In plain words
What is it for?
It guides context managers for files and other resources and Pydantic Settings for structured configuration.
Why use it?
It helps an agent follow the existing project's patterns instead of introducing different ways to open resources or store settings.

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/steph-dove/klaussy-agents/scripts
Clone the repo
git clone --depth 1 https://github.com/steph-dove/klaussy-agents

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 220 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.00220
Opus 5 $0.00000 $0.00110
Sonnet 5 $0.00000 $0.00044
Haiku 4.5 $0.00000 $0.00022

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

Security

Grade A, and why

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

examples/fastapi/.cursor/rules/scripts.mdc · 30 lines

What it actually says

Conventions

  • Context manager usage: Manage resource lifecycles using context managers (e.g., Use context managers for resource management. 37 with statements (23 sync, 14 async). Types: file_io (4), threading (2).). Example context from scripts/docs.py (lines 853-859):
        in_code_block4 = False
        permalinks = set()
    
        with path.open("r", encoding="utf-8") as f:
            lines = f.readlines()
    
        for line in lines:
    
  • Structured configuration with Pydantic Settings: Use Pydantic BaseSettings for configuration management. Example context from scripts/label_approved.py (lines 12-18):
        number: int
    
    
    default_config = {"approved-2": LabelSettings(await_label="awaiting-review", number=2)}
    
    
    class Settings(BaseSettings):
    
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 · 30 lines · 0 tokens per session scan A e9767564900d

Subscribe to this mod's changes

scripts is a cursor rule published in the GitHub repository steph-dove/klaussy-agents (15 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 220 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.