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/cycloidio/cycloid-mcp-server/global-developmentgit clone --depth 1 https://github.com/cycloidio/cycloid-mcp-serverWhat 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.00000 | $0.00974 |
| Opus 5 | $0.00000 | $0.00487 |
| Sonnet 5 | $0.00000 | $0.00195 |
| Haiku 4.5 | $0.00000 | $0.00097 |
Grade A, and why
global-development 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.
How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cycloid MCP Server - Global Development Rules
You are an expert in Python backend development and core system architecture, specifically for the Cycloid MCP Server.
Key Principles
- Follow existing file structure patterns
- Ensure comprehensive test coverage
- Keep documentation up-to-date
- Write clean, maintainable code
- Use Python's features effectively
- Implement proper error handling
- Optimize for performance
- Follow SOLID principles
- Keep memory usage efficient
- Write clear changelogs
Code Quality & Development Standards
1. Type Checking with Pyright
- Always run pyright before committing code
- Use comprehensive type hints throughout the codebase
- Avoid using
Anytype - prefer specific types - Use
from typing importfor complex types - Ensure all functions have proper return type annotations
- Use
pyright --strictfor maximum type safety
2. Testing Requirements
- Write unit tests for all changes
- Include integration tests
- Test edge cases
- Maintain test coverage
- Use pytest effectively
- Run
make testto ensure all tests pass - Update test imports when refactoring
3. Code Quality
- Write clean, maintainable code
- Use type hints consistently
- Follow PEP 8 guidelines
- Keep functions focused and small (under 50 lines when possible)
- Minimize code duplication
- Prefer functional programming patterns where appropriate
- Use meaningful variable and function names
4. Python Features
- Use async/await effectively
- Implement proper error handling
- Use context managers (
withstatements) - Leverage Python's standard library
- Use dataclasses where appropriate
- Use type annotations for all function parameters and return values
5. Error Handling
- Use custom exceptions from
src.exceptions - Implement proper error recovery
- Provide meaningful error messages
- Log errors appropriately using
structlog - Use early returns for error conditions
- Avoid deeply nested try/except blocks
6. Performance & Memory
- Optimize memory usage
- Use generators for large datasets
- Implement proper cleanup
- Monitor memory consumption
- Use async operations for I/O
- Implement caching where appropriate
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.
- yesterday First seen · 160 lines · 974 tokens per session scan A ca5f267422b8
global-development is a cursor rule published in the GitHub repository cycloidio/cycloid-mcp-server (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 974 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.