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.
npx agentmods add rules/mayurnarang9099-maker/snow-azure-githubmcp/cursorrulesgit clone --depth 1 https://github.com/mayurnarang9099-maker/snow-azure-githubMCPWhat 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 | $0.00660 | $0.00660 |
| Opus 5 | $0.00330 | $0.00330 |
| Sonnet 5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
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 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.
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.
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:
- Standard library imports
- Third-party imports
- 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
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.
- 2d ago First seen · 83 lines · 660 tokens per session scan A 295fb9128401
cursorrules is a cursor rule published in the GitHub repository mayurnarang9099-maker/snow-azure-githubMCP (0 stars, last pushed 4mo 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.
Other cursor rules, from other repositories
python_tests
We use the unit tests to cover internal behavior that can work without the web / backend counterpart. We aim for 95%+ unit test coverage of our Python code in lib/streamlit.
fastapi-production-architecture-cursorrules-prompt-file
Cursor rules for FastAPI services with router/service/repository boundaries, typed provider adapters, bulkhead isolation, idempotency, and domain exceptions.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
sqlmodel
Satisfying the type checker when working with SQLModel.
python
Python开发规则 - Python最佳实践和项目结构 (python, pip, django, flask, fastapi).
backend-python
Cursor rule "backend-python" from coeusyk/inference-x, covering backend python rules, stack assumptions, code style, fastapi conventions and schema conventions.