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/core-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.00658 |
| Opus 5 | $0.00000 | $0.00329 |
| Sonnet 5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
core-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.
What it actually says
You are an expert in Python backend development for the Cycloid MCP Server using FastMCP 3.0.
Key Principles
- Use standalone
@tool()and@resource()decorators (not class-based MCPMixin) - Inject CLIMixin via
Depends(get_cli)fromsrc.dependencies - Use
ToolErrorfromfastmcp.exceptionsfor tool-level errors - Leverage centralized type definitions from
src.types - Apply proper import organization (stdlib → third-party → local)
- JSON-only output (no table formatting)
- Follow FastMCP logging with
get_loggerfromfastmcp.utilities.logging
Core Development Guidelines
-
Architecture Patterns
- Components are plain async functions in
src/components/— auto-discovered by FileSystemProvider - No base classes, no MCPMixin, no ComponentRegistry
- CLI injection via
Depends(get_cli)— never instantiate CLIMixin directly in tools - Use
execute_cli_commandwithauto_parseparameter for CLI calls - Use
process_cli_responsefor standardized response processing
- Components are plain async functions in
-
Type Safety & Imports
- Import common types from
src.types(JSONDict, JSONList, CliFlags, OptionalString, etc.) - Import order: stdlib → third-party → local (
src.) - FastMCP
Dependsimport needs# type: ignore[reportAttributeAccessIssue] Depends(get_cli)defaults need# type: ignore[reportCallInDefaultInitializer]
- Import common types from
-
Error Handling
- Use
ToolErrorfromfastmcp.exceptionsfor validation errors, not-found, etc. - Use
CycloidCLIErrorfromsrc.exceptionsfor CLI execution failures - Log with
get_logger(__name__)fromfastmcp.utilities.logging
- Use
-
CLI Integration
- Use
execute_cli_commandwithauto_parse=Truefor parsed JSON responses - Use
execute_cli_commandwithauto_parse=Falsefor raw CLIResult - Use
process_cli_responsefor consistent response handling - Never cache CLI API responses (dynamic data)
- Output format is always JSON (hardcoded
--output json)
- Use
-
Testing
- Use pytest + pytest-asyncio with FastMCP's
Client - Register functions via
server.add_tool()/server.add_resource() - Mock CLIMixin with
@patchandAsyncMock - Tool errors raise
ToolErrorexceptions in client
- Use pytest + pytest-asyncio with FastMCP's
-
Code Quality
- Pyright strict mode (
pyrightconfig.json) - black (88 char), isort (black profile), flake8 (100 char max)
- Python 3.12+ (CI runs 3.13)
- Pyright strict mode (
Dependencies
- Python 3.12+
- FastMCP 3.0+
- pytest, pytest-asyncio
- pyright, flake8, black, isort
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 · 61 lines · 658 tokens per session scan A ba577906421b
core-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 658 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.