cursorrules

A set of written rules for organising a Python project, including its folders, file names, and imports.

In plain words
What is it for?
Use it when creating or reviewing a Python project with source code, tests, documentation, examples, scripts, and configuration files.
Why use it?
It gives coding agents a consistent project layout to follow, reducing confusion about where code and tests belong.

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/chrisww2/now-mcp/cursorrules
Clone the repo
git clone --depth 1 https://github.com/chrisww2/now-mcp

Made for: Cursor.

Per session 660 This file is loaded in full into every session.
When invoked 660 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% 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.00660 $0.00660
Opus 5 $0.00330 $0.00330
Sonnet 5 $0.00132 $0.00132
Haiku 4.5 $0.00066 $0.00066

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

Security

Grade A, and why

cursorrules 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

100% identical to cursorrules — 0 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.

.cursorrules · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Python project structure rules

This file defines the structure for a Python project with similar organization to the ServiceNow MCP project

Root directory structure

root/ ├── src/ # Source code directory │ └── servicenow_mcp/ # Main package directory │ ├── init.py # Package initialization │ ├── server.py # Server implementation │ ├── cli.py # CLI implementation │ ├── auth/ # Authentication related code │ ├── tools/ # Tool implementations │ ├── utils/ # Utility functions │ └── resources/ # Resource definitions ├── tests/ # Test directory │ ├── init.py │ └── test_*.py # Test files ├── docs/ # Documentation ├── examples/ # Example code ├── scripts/ # Utility scripts ├── .env # Environment variables ├── .gitignore # Git ignore rules ├── LICENSE # License file ├── README.md # Project documentation ├── pyproject.toml # Project configuration └── uv.lock # Dependency lock file

File naming conventions

*.py:

  • Use snake_case for file names
  • Test files should start with test_
  • Main package files should be descriptive of their purpose

Directory naming conventions

directories:

  • Use snake_case for directory names
  • Keep directory names lowercase
  • Use plural form for directories containing multiple items

Import structure

imports:

  • Group imports in the following order:
    1. Standard library imports
    2. Third-party imports
    3. Local application imports
  • Use absolute imports for external packages
  • Use relative imports for local modules

Testing conventions

tests:

  • Each test file should correspond to a module in the source code
  • Test classes should be prefixed with Test
  • Test methods should be prefixed with test_
  • Use pytest fixtures for common setup

Read the full file on GitHub · 83 lines

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 · 83 lines · 660 tokens per session scan A 295fb9128401

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository chrisww2/now-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 660 tokens to every session, about $0.0033 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cursorrules, differing in 0 lines, and is treated as a copy.