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/QuincyMillerDev/ilograph-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/quincymillerdev/ilograph-mcp-server/python)<a href="https://agentmods.dev/rules/quincymillerdev/ilograph-mcp-server/python"><img src="https://agentmods.dev/badge/rules/quincymillerdev/ilograph-mcp-server/python/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/quincymillerdev/ilograph-mcp-server/python"><img src="https://agentmods.dev/badge/rules/quincymillerdev/ilograph-mcp-server/python.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.01189 | $0.01189 |
| Opus 5.5 | $0.00476 | $0.00476 |
| Sonnet 5.5 | $0.00238 | $0.00238 |
| Haiku 4.5 | $0.00119 | $0.00119 |
Grade A, and why
python 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert in Python, FastMCP, and scalable MCP server development.
Key Principles
- Write concise, technical responses with accurate Python examples.
- Use functional, declarative programming; avoid classes where possible except for custom error types.
- Prefer iteration and modularization over code duplication.
- Use descriptive variable names with auxiliary verbs (e.g., is_active, has_permission).
- Use lowercase with underscores for directories and files (e.g., tools/data_tools.py).
- Favor named exports for tools, resources, and utility functions.
- Use the Receive an Object, Return an Object (RORO) pattern where applicable.
- DO NOT MAKE ASSUMPTIONS
Python/FastMCP
- Use def for function definitions with proper type hints.
- Use type hints for all function signatures where possible.
- File structure: MCP server initialization, tools, resources, prompts, utilities, config.
- Avoid unnecessary curly braces in conditional statements.
- For single-line statements in conditionals, omit curly braces.
- Use concise, one-line syntax for simple conditional statements (e.g., if condition: do_something()).
- Prefer async/await for I/O operations and external API calls.
Error Handling and Validation
- Prioritize error handling and edge cases:
- Handle errors and edge cases at the beginning of functions.
- Use early returns for error conditions to avoid deeply nested if statements.
- Place the happy path last in the function for improved readability.
- Avoid unnecessary else statements; use the if-return pattern instead.
- Use guard clauses to handle preconditions and invalid states early.
- Implement proper error logging and user-friendly error messages.
- Use custom error types or error factories for consistent error handling.
- Handle MCP protocol errors gracefully and return meaningful responses.
Dependencies
- FastMCP (core MCP server framework)
- Pydantic (for data validation and serialization)
- httpx or aiohttp (for async HTTP requests)
- pathlib (for file system operations)
- typing (for advanced type hints)
FastMCP-Specific Guidelines
- Use FastMCP decorators for exposing functionality:
@mcp.tool()for executable functions (like POST endpoints)@mcp.resource()for data exposure (like GET endpoints)@mcp.prompt()for reusable interaction templates
- Organize MCP capabilities using clear separation of concerns.
- Use descriptive names for tools, resources, and prompts that clearly indicate their purpose.
- Implement proper docstrings for all MCP-exposed functions as they serve as descriptions.
- Use FastMCP's built-in validation and error handling capabilities.
- Leverage FastMCP's automatic protocol handling rather than implementing low-level MCP details.
- Use FastMCP's client capabilities for server-to-server communication when needed.
- Implement proper logging using Python's logging module.
Performance Optimization
- Use async/await for I/O-bound operations to avoid blocking.
- Implement caching for frequently accessed resources.
- Use connection pooling for external API calls.
- Implement proper session management for stateful operations.
- Use background tasks for time-consuming operations when appropriate.
- Consider resource lifecycle management (setup/teardown) for expensive resources.
Key Conventions
- Use clear, descriptive function names that indicate the tool/resource purpose.
- Prioritize MCP server performance metrics (response time, resource availability).
- Structure the application:
- Use modular organization for different capability areas.
- Implement clear separation between tools, resources, and business logic.
- Use environment variables for configuration management.
- Group related functionality into logical modules.
Data Handling and Validation
- Use Pydantic models for complex data structures and validation.
- Implement proper input validation for all tool parameters.
- Use type hints extensively for better IDE support and runtime validation.
- Handle different data formats (JSON, text, binary) appropriately.
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 · 125 lines · 1,189 tokens per session scan A 4702c121ffa5
python is a cursor rule published in the GitHub repository QuincyMillerDev/ilograph-mcp-server (3 stars, last pushed 11mo ago), licensed MIT. It adds 1,189 tokens to every session, about $0.0048 per session on Opus 5.5. 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.
django-python
Rules for writing Python services at PostHog (Python servers powered by the Django framework).
py-fast-api
Cursor rules for Python FastAPI backend development and best practices.
python
Python best practices and patterns for modern software development with Flask and SQLite.
python--typescript-guide-cursorrules-prompt-file
Cursor rules for Python development with TypeScript guide integration.
python-conventions
Python coding style, FastAPI endpoint template, code organisation sections.