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.
git clone --depth 1 https://github.com/cycloidio/cycloid-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/cycloidio/cycloid-mcp-server/pyright)<a href="https://agentmods.dev/rules/cycloidio/cycloid-mcp-server/pyright"><img src="https://agentmods.dev/badge/rules/cycloidio/cycloid-mcp-server/pyright/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/cycloidio/cycloid-mcp-server/pyright"><img src="https://agentmods.dev/badge/rules/cycloidio/cycloid-mcp-server/pyright.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.03985 |
| Opus 5.5 | $0.00000 | $0.01594 |
| Sonnet 5.5 | $0.00000 | $0.00797 |
| Haiku 4.5 | $0.00000 | $0.00398 |
Grade A, and why
pyright 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pyright and BasedPyright Best Practices: A Comprehensive Guide
This guide provides comprehensive best practices for using pyright and BasedPyright in Python projects. These practices cover code organization, design patterns, performance optimization, security considerations, testing strategies, common pitfalls, and recommended tooling.
1. Code Organization and Structure
1.1 Directory Structure Best Practices
-
Flat vs. Nested: Choose a directory structure that balances simplicity and maintainability. For small projects, a flat structure might suffice. For larger projects, a nested structure that mirrors the module hierarchy is often better. For example:
my_project/ ├── src/ │ ├── my_module/ │ │ ├── init.py │ │ ├── file1.py │ │ ├── file2.py │ ├── main.py ├── tests/ │ ├── my_module/ │ │ ├── test_file1.py │ │ ├── test_file2.py │ ├── conftest.py ├── pyrightconfig.json ├── pyproject.toml (or setup.py/setup.cfg) ├── README.md
-
srcLayout: Use thesrclayout to separate application code from project metadata. This helps prevent accidental imports of test or configuration files.
1.2 File Naming Conventions
- Python Naming: Follow standard Python naming conventions (PEP 8):
- Modules:
lowercase_with_underscores.py - Classes:
PascalCase - Functions and variables:
lowercase_with_underscores - Constants:
UPPERCASE_WITH_UNDERSCORES
- Modules:
- Test Files: Name test files consistently, e.g.,
test_<module_name>.pyor<module_name>_test.py.
1.3 Module Organization
- Cohesion: Group related functions and classes within a single module.
- Coupling: Minimize dependencies between modules to improve maintainability.
__init__.py: Use__init__.pyfiles to define packages and control namespace imports. Consider explicit relative imports within packages (e.g.,from . import moduleinstead ofimport module).
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.
- 1mo ago First seen · 292 lines · 3,985 tokens per session scan A a79215c8e8d7
pyright is a cursor rule published in the GitHub repository cycloidio/cycloid-mcp-server (0 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,985 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-31.
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.
python-llm-ml-workflow-cursorrules-prompt-file
Cursor rules for Python LLM & ML development with workflow integration.
python
Python best practices and patterns for modern software development with Flask and SQLite.
python-containerization-cursorrules-prompt-file
Cursor rules for Python development with containerization integration.
python-django-general
General coding guidance for Python and Django projects, including naming, formatting, modular apps, built-in tools, and maintainable structure. Python is a programming language, and Django is a Python web framework.
python-general-coding-standards
A set of general standards for Python projects, including type hints, input checking, code style, security, web requests, background work, and tests. It also covers FastAPI-specific tasks such as CORS and authentication.